On 2/7/07, Kees Cook <kees@...62...> wrote:
On Sat, Feb 03, 2007 at 06:12:56PM -0800, Bryce Harrington wrote:
I think it would be great to see the following build system problems solved: [snip]
I'll throw in my $0.02 too... If the current build system were replaced, I'd like to not lose one specific feature: fully parallel builds. At present, given the "single Makefile in src/", I can actually use all 4 CPUs to do compiles, etc. I don't want to regress to having a separate Makefile in every subdirectory. :)
I will have to look into this but i don't there will be a problem with using all available processors to compile. As to the seperate Makefiles in every subdirectory they would be a cmakelist.txt but they would all be included into the main cmakelist.txt in the src directory. this can be avoid by setting all the sub-projects in the same cmakelist.txt file but doing this IMO would make the build files a more of a hassle to work with.
Joshua L. Blocher verbalshadow
-- Kees Cook @outflux.net
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Wednesday 07 February 2007 18:37:51 Joshua Blocher wrote:
On 2/7/07, Kees Cook <kees@...62...> wrote:
On Sat, Feb 03, 2007 at 06:12:56PM -0800, Bryce Harrington wrote:
I think it would be great to see the following build system problems solved: [snip]
I'll throw in my $0.02 too... If the current build system were replaced, I'd like to not lose one specific feature: fully parallel builds. At present, given the "single Makefile in src/", I can actually use all 4 CPUs to do compiles, etc. I don't want to regress to having a separate Makefile in every subdirectory. :)
I will have to look into this but i don't there will be a problem with using all available processors to compile. As to the seperate Makefiles in every subdirectory they would be a cmakelist.txt but they would all be included into the main cmakelist.txt in the src directory. this can be avoid by setting all the sub-projects in the same cmakelist.txt file but doing this IMO would make the build files a more of a hassle to work with.
Why would having a makefile in each subdirectory break that, even with autotools?
I know if I run make -j3 with Scribus, the autotools build will also start to build plugins which are 2 subdirectories under the main source directories alongside the main directory?
This works the same way with cmake. I think you are better off with a cmakelist.txt file in each dir.
Craig
On Thu, Feb 08, 2007 at 08:50:13PM +0100, Craig Bradney wrote:
I know if I run make -j3 with Scribus, the autotools build will also start to build plugins which are 2 subdirectories under the main source directories alongside the main directory?
Maybe autotools/make has improved, but prior to the one-big-Makefile changes in inkscape, it would only compile things per-directory. But as long as the build is faster, I don't care what system is used to compile it. :)
participants (3)
-
Craig Bradney -
Joshua Blocher -
Kees Cook