Well, the #include <SDL/SDL.h> syntax doesn’t work on MacOS because
the Macintosh filesystem uses the ‘:’ directory separator character.
I’m thinking about moving the include syntax from <SDL/SDL.h> to "SDL.h"
Old code would of course work properly on UNIX, because the sdl-config
script will output the proper include directories, but code intended to
be portable to other OS’s should use the new convention.
Well, the #include <SDL/SDL.h> syntax doesn’t work on MacOS because
the Macintosh filesystem uses the ‘:’ directory separator character.
I’m thinking about moving the include syntax from <SDL/SDL.h> to "SDL.h"
Old code would of course work properly on UNIX, because the sdl-config
script will output the proper include directories, but code intended to
be portable to other OS’s should use the new convention.
Comments?
Who told you that?
CodeWarrior has an option “Interpret DOS and UNIX paths” which works.
Then again, the docs only show this working #include "dir/header.h"
and not #include <dir/header.h>
Well, the #include <SDL/SDL.h> syntax doesn’t work on MacOS because
the Macintosh filesystem uses the ‘:’ directory separator character.
I’m thinking about moving the include syntax from <SDL/SDL.h> to "SDL.h"
Old code would of course work properly on UNIX, because the sdl-config
script will output the proper include directories, but code intended to
be portable to other OS’s should use the new convention.
Comments?
Who told you that?
CodeWarrior has an option “Interpret DOS and UNIX paths” which works.
Then again, the docs only show this working #include "dir/header.h"
and not #include <dir/header.h>
I’m using Apple MPW.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Well, the #include <SDL/SDL.h> syntax doesn’t work on MacOS because
the Macintosh filesystem uses the ‘:’ directory separator character.
Macs really don’t support / in #include??? Windows supports / even
though its separator is …–
Pierre Phaneuf
Ludus Design, http://ludusdesign.com/
“First they ignore you. Then they laugh at you.
Then they fight you. Then you win.” – Gandhi
Any particular reason you are using MPW? (Not that it is bad)
I don’t have a recent version of CodeWarrior, so I’m using MPW
for primary development, and other people (better Mac coders
are submitting Codewarrior projects.
Well in that case what you propose is the best solution most likely.
I don’t have a recent version of CodeWarrior, so I’m using MPW
for primary development, and other people (better Mac coders
are submitting Codewarrior projects.
I really like MPW. It is free (in cost), always a plus. And Apple
actively maintains it, with regular updates. It is much more unixish
than CodeWorrier. If you also install perl (of course), dmake (more
"conventional" than MPW make), gcc (really!), and a handful of GNU
utilities (grep, m4, awk, whatever you use) you have an environment that
is VERY friendly to cross-platform development. The same reason I use
mingw32.
Unless, of course, you use CodeWarrior on Linux and Windows. :)–
Max Watson <@Max_Watson>
Resident Cartographer and Code Guy
