Caleb Epstein wrote:
> On Tue, 01 Mar 2005 11:15:44 +0100, Joerg Thoennes
> <Joe...@ma...> wrote:
>
>>You could also use 3 copies to build it for 3 systems or just do something like
>>Actually I do not understand why you need to do it this very special way.
>
> Several reasons come to mind:
>
> * Time. If the code can be compiled in an external directory, Bill
> could kick off all three architectures to build in parallel.
> * Convention. Most GNU tools can be built this way. GCC specifically
> comes to mind.
> * Separation. Its much easier to cleanup the build artifacts and be
> sure that your source code is pristine and unmodified if you build in
> a separate directory. You can even make the sources read-only.
Agreed. The posted reminded me vaguely of the GNU software build feature and I quickly
browsed the autotools, but did not find any pointers how to implement this in QF. So I
just asked why Robert does need this. You gave the more constructive answer. Thanks.
> None of these are earth-shattering, but it might be nice if QuickFIX
> supported this. I'm another person who builds QF on multiple
> architectures (only two) and frequently test patches to the code so I
> frequently need to reconfigure and recompile in the same source tree.
> I would like the ability to have a separate build dir to make this a
> simpler job (and one that didn't require re-configure'ing when
> changing architectures).
Also spoke to Robert about this. We just need some GNU tool works this way and check in
which place the QF build setup differs. Any suggestions?
Cheers, Jörg
--
Joerg Thoennes
http://macd.com
Tel.: +49 (0)241 44597-24 Macdonald Associates GmbH
Fax : +49 (0)241 44597-10 Lothringer Str. 52, D-52070 Aachen
|
