Hello Synfig devs, I was writing Makefile.debian files for ETL and synfig-core. I noticed that ETL is just copied from the source dir to the install dir, with some configuration in etl_profile.h.
Would it be helpful or unhelpful for the project if I patched ETL so that it was a static library, not just a set of headers, linked in by synfig-core and synfig-studio? My reasons are these: * ETL classes would only be compiled once, instead of for every file that includes them. That would speed up compilation on low-end boxes. * Configuration #ifdef would be unnecessary in ETL, because the Makefile or ./configure would choose the right C++ sources based on the platform. That is, either etl_thread_pthread.cpp or etl_thread_win32.cpp would be picked. A single etl_thread.h could then be used for both operating systems. If there is some reason that this would not be accepted, that is OK. I was concerned about compilation speed because I run gNewSense GNU/Linux in a rinky-dink MIPS-based laptop. Thanks, faraway ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
