Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
It would be great if mdtool supported locating sources outside of the source tree during the build. This is something supported by autotools, cmake etc and mdtool is one tool that doesn't seem to make this easy, unless I'm missing something.
Can you please clarify what you mean by this? mdtool just builds what's specified in the project file.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
What I was looking for was a way to specify the output location of the files so I could put all of the generated files into a directory outside of the source tree. The CMake guys describe it like http://www.cmake.org/Wiki/CMake_FAQ#What_is_an_.22out-of-source.22_build.3F
The idea is mostly that if you want to ensure everything is rebuilt you can very easily remove the directory used for building and be sure that everything generated has been removed. Vs. worrying about dependencies being updated correctly, 'make clean'-like things etc.
We won't be adding features like this to mdtool, since we're gradually migrating to the MSBuild build engine, which does support this kind of thing.
Oh ok. I've been a bit out of the loop on mono stuff the last few years. I'm a huge fan and hope it continues and has continued corporate support as well.