And here is more fun! Try this!! First, lets compile Felix down to C++ and capture the C++ in the directory flxout:
~/felix>flx --nocc --bundle_dir=flxout src/flx/flx ~/felix>ls flxout flx.cpp flx.hpp flx.rtti flx.ctors_cpp flx.includes flx_static_link_thunk.cpp flx.dep flx.resh It's worth: ~/felix>cat flxout/flx.resh flx_strutil flx_ioutil re2 flx flx_gc Now we note this: ~/felix>build/release/bin/flx_pkgconfig --rec --field=provides_slib --path=build/release/config @flxout/flx.resh -lflx_static -lflx_gc_static -ljudy_static -lflx_pthread_static -lflx_exceptions_static -lflx_re2_static And we try this: clang++ --std=c++11 -Wno-invalid-offsetof -o nuflx \ -Iflxout -Ibuild/release/config/target -Ibuild/release/lib/rtl \ -Lbuild/release/lib/rtl \ -lflx_gc_static -lflx_static -ljudy_static -lflx_re2_static -lflx_exceptions_static -lflx_pthread_static \ flxout/flx.cpp \ flxout/flx_static_link_thunk.cpp \ build/release/lib/rtl/flx_run_lib.o \ build/release/lib/rtl/flx_run_main.o AND IT WORKS! What does this mean? It means we can build "flx" directly from the generated C++ source without using "flx" to build it. In particular, we do not need to ship the binary "flx" in the bootstrap. There's a good chance ALL the tools can be shipped this way. (except flxg). -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language