A two liner that won't compile on CW 9.5

Dear NG

I need to add to a Photoshop plugin a function that takes an std::string
argument and creates a folder hierarchy using mkdir(). I am starting to
think this is not doable with CW 9.5 :

Config : I have CW 9.5 + Mac OSX Universal SDK 10.4

Issue : The following two lines will not compile :
#include <fstat.h>
#include <string>

with access paths set to
{Compiler}MSL/MSL_C (recursive)
{Compiler}MSL/MSL_C++ (recursive)
{Compiler}MSL/MSL_Extras/MSL_Common (recursive)
{OS X Volume}usr/include (not recursive)

Symptom : CW complains that identifier dev_t is redeclared (and gid_t
etc...)

I have exhausted all the combinations of access path order / #include
order etc : No matter what, some identifier is redefined or missing or
some include path is not found.

My question is thus:
What should be the target settings / #include order to compile those two
lines (which are merely a prerequisite for writing the function I need)
?

I believe that the problem is much deeper than it seems and that I am
unwittingly mixing MSL headers with BSD headers and that this is not
supported by CW (or at least only partially supported). However, I
cannot figure where this happens and how to avoid it.

Thanks for your help.
_______________________________________________________
François Robert
(to mail me, reverse character order in reply address)

In article ,
"François Robert" wrote:

> Dear NG
>
> I need to add to a Photoshop plugin a function that takes an std::string
> argument and creates a folder hierarchy using mkdir(). I am starting to
> think this is not doable with CW 9.5 :
>
> Config : I have CW 9.5 + Mac OSX Universal SDK 10.4
>
> Issue : The following two lines will not compile :
> #include <fstat.h>
> #include <string>
>
> with access paths set to
> {Compiler}MSL/MSL_C (recursive)
> {Compiler}MSL/MSL_C++ (recursive)
> {Compiler}MSL/MSL_Extras/MSL_Common (recursive)
> {OS X Volume}usr/include (not recursive)
>
> Symptom : CW complains that identifier dev_t is redeclared (and gid_t
> etc...)
>
> I have exhausted all the combinations of access path order / #include
> order etc : No matter what, some identifier is redefined or missing or
> some include path is not found.
>
> My question is thus:
> What should be the target settings / #include order to compile those two
> lines (which are merely a prerequisite for writing the function I need)
> ?
>
> I believe that the problem is much deeper than it seems and that I am
> unwittingly mixing MSL headers with BSD headers and that this is not
> supported by CW (or at least only partially supported). However, I
> cannot figure where this happens and how to avoid it.
>

Checking /Developer/SDKs/MacOSX10.3.9.sdk and
/Developer/SDKs/MacOSX10.4u.sdk with:

find . -name "*stat.h" -print

shows that fstat isn't part of either SDK. Checking the MSL folder
inside the Codewarrior folder shows that it doesn't have an fstat.h
either.

Lastly, a check of /usr/include also fails to find an fstat.h

man fstat

shows that fstat wants:
#include <sys/types.h>
#include <sys/stat.h>

Adding those to a the HelloWorld.cp of a new "C++ console Mach-O" style
C++ project shows it compiles with no problems. (I've got

"OS X Volume" set to /Developer/SDKs/MacOSX10.3.9.sdk on the Source
Trees panel of the IDE preferences.

I also tried it with "OS X Volume" set to / in the project's
Preferences' Source Tree panel.

I can't make it fail!