Hi Marcus,
Marcus Lindblom wrote:
>
> Yup. Changing fcd2code so that it generates external include guards
> should be quite easy, and helpful, in terms of compilation perf.
I don't know. Has anybody run those kinds of tests with 2005? The gcc results
indicate that it's very possible to make external and internal ones perform
equally well, so MS might have done the same thing.
> I have also been toying with the idea of rewriting the
> #include-statements in OpenSG to use a path with dirs relative to the
> source-directory. That'd make the compiler only have one root include
> path for OpenSG-libs, and since we're rewriting the include-files on
> export anyway, it's not a problem to have a single include-dir for end
> users as we do today.
>
> It'd also make the build scripts a tiny bit simpler since you don't need
> to add all those include-paths. The output would be reduced. (Each
> compiled file in system takes up almost half a screen of text currently.)
>
> Does it sound reasonable?
That's the way 2 is anyway, to reflect the installation structure already
during
build. Given that you get a direectory with lots of files it might not have a
positive impact on performance, but the compile lines sure looks nicer. ;)
Dirk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
