Hi Marcus,
On Wed, 2006-03-15 at 14:27 +0100, Marcus Lindblom wrote:
>
> I looked it (in Common/DefaultRules.mk) and it looks complicated,
> especially me not being overly familiar with make/perl (i.e. I don't
> know the difference between @ and $ in the makefile). I've fiddled with
> sed though.
It's not really that complicated, as you can reuse most of the existing
code. The problem is finding out what the text is for header and source
files and for the custom build rules for flex/bison and install. All of
that is in the print statement in createDSPSourcePart.pl
> Furthermore, it looks like it creates .dsp, when visual 2003 & 2005
> usually uses .vcproj?
Given that VS.Net can import dsw/dsp directly it was quicker to just
write dsw/dsp using the correct options for the new compilers.
Hm, actually the VS8 dailybuild that I set up the other day should have
usable VS8 project files, so maybe those are good enough for now.
Dirk
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
