On Wed, 2011-03-30 at 21:19 +0200, Darius Blaszyk wrote: > On Mar 30, 2011, at 9:08 PM, Michael Van Canneyt wrote: > >> On Mar 30, 2011, at 5:31 PM, michael.vancann...@wisa.be wrote: > >> > >>>> - managing debug/release builds (also cross-compiling) > >>> > >>> What is failing in the current system for this ? > >> > >> I was thinking to be able to do something like : > >> > >>> fpmake build debug > >> > >> This will add some debug options to the build process. Also it should be > >> possible to create a custom build profile. > > > > And how would you do this ? > > > > I don't want to complicate fpmake unnecessarily. > Improve the command line paring algorithm. It should check if there is > something behind the build command line option. If so then it is a named > build profile. In fpmake you could check the TDefaults.Profile property to > determine which options to add.
I step in too late to avoid some long discussions, but here I go: This feature is already there. When you use fpmake directly: -f, if you use fppkg (what I would recommend): fppkg -c. When I want to do a cross-build I can do: fppkg build -c win32 fppkg build -c i386-linux fppkg build -c 244 (use another compiler-version) fppkg build -c debug (well, not cross, but debug-information...) Use 'fppkg listsettings'. It shows which configuration-file it uses, and where you can store your custom configuration-files. (Or 'profiles', if you like that term) Joost. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
