<div class="gmail_quote">2010/7/5 John Drescher <span dir="ltr"><<a href="mailto:drescherjm@gmail.com" target="_blank">drescherjm@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>> I see, thanks. I intend to write a Python script that adds the extra<br>
> platform solution, because we really need that. Visual Studio and<br>
> Code::Blocks project files are XML files, so it shouldn't be too hard.<br>
><br>
<br>
</div>What is wrong with different build folders for each compiler / ide?<font color="#888888"><br></font></blockquote><div> </div><div>(sorry for picking this up again so late)<br><br>We do have different build
folders for each compiler / ide, but I mean 'build folder' as the folder where the object files and executable ends. We just want one project file with
different platform solutions, so we don't have to reload the project
file when we want to switch. Having two project files in the same
solution also is not an option, because the source files and many
settings are the same. Besides, this is a big solution file with over 50
project files, so doubling that would make things a lot harder.<br>
</div></div><br>I don't really understand why some find this an awkward way of doing things, it is simply convenient to have both platforms in one project file, e.g. it is easy to build everything at once. I don't see any drawbacks.<br>
<br>Mark<br>