http://www.riscos.info/bugzilla3/show_bug.cgi?id=180
John Tytgat <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |REMIND --- Comment #2 from John Tytgat <[email protected]> 2010-01-20 17:30:34 --- In case we're going beyond the changes Peter made as outlined in #1 and would really consider adding $GCCSDK_INSTALL_ENV/{lib,include} to our gcc's default library and include paths, a couple of concerns: 1. Currently we're able to build one cross-compiler and use it for different GCCSDK_INSTALL_ENV settings (e.g. library builds for module code vs application code, debugging & testing the compiler). When GCCSDK_INSTALL_ENV is going to get built in the cross-compiler we're going to need a separate build for each GCCSDK_INSTALL_ENV setting. 2. I'm unsure what implications this would have on building the RISC OS native compiler. This needs to be at least checked. 3. It would involve additional patches to gcc tree which is not really desired. -- Configure bugmail: http://www.riscos.info/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
