http://www.riscos.info/bugzilla3/show_bug.cgi?id=180
--- Comment #3 from Peter Naulls <[email protected]> 2010-01-22 08:57:38 --- My understanding of such changes from what I've gathered from other setups is that these additional paths are purely configuration options that would be specified to the cross compiler only, and not toolchain patches at all. But I've not been able to determine where such configuration would be. The situation for native compilers is related, although can be somewhat ignored in the immediate situation, since only the most simple of Makefiles from Unix would be run on RISC OS as well, unless we share a Makefile that works on both, but in general we would tend to be using explicit RISC OS path syntax for both -L and -I. Having said that, GCC could be made to look for a general include/library path. And then development applications (e.g !DeskLib) could add themselves to it. In this case, the compiler configuration would be the same mechanism as that advocated above for the cross case. -- 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
