[openbeos] Re: Compiling Haiku On Windows...

On Fri, 18 Nov 2005, Axel [iso-8859-15] Dörfler wrote:
Mathew Schofield <mr.skoe@xxxxxxxxx> wrote:
[...] 
With Windows! Now, i'm pretty "slow" in some areas, but im trying...
Now, there is a utility for Windows called Cygwin which tries to give
Windows POSIX compatability (Amoung other things). It also allows
Unix/Linux apps to be compiled for Windows. I am currently setting up
cygwin to compile Haiku, and so far i have [slowly] managed to create
a toochain.
Next step is actually compiling haiku, and i have sort of ran into a
few "bumps", and what not.
1) Could someone please add "CYGWIN_NT-5.0" as a build target in the
configure script?
[ Just the same as fbsd/linux: "CYGWIN_NT-5.1) buildPlatform=linux
;;"]

I'm not really happy with Nathan's change for freebsd here. If it is a different platform, it should be identified respectively. There are only like five or six occurrences in build/jam/BuildSetup, where the platform is checked. Those should be extended to support new platforms.

2) In src/build/libroot/errors.cpp, could someone change
ADD_ERROR(ECANCELED);

 (About line 78) to

 #ifdef ECANCELED
  ADD_ERROR(ECANCELED);
 #endif


I would rather wait with that until it actually works - for now, just
keep your changes local. When you're done, you can submit a patch
(using diffs).

Yep, that would be preferrable.
Regarding ECANCELED, I would rather not add the change. Instead ECANCELED should be defined to something usable in headers/build/BeOSBuildCompatibility.h, if it doesn't exist.

3) I'm getting a nothrow undeclared error in
"headers/build/private/app/MessageBody.h:148" and
"headers/build/private/app/MessageBody.h:443"

For some wierd reason no matter what i do (using std::nothrow, etc.)
it still says undeclared. "using namespace std;" is in the file, and
yet changing "nothrow" to "std::nothrow" fixes it! Why? (lol).

Are you including <new>?

<new> is not yet included in the header file as it exists in the repository. I will soon fix the problems there are with host gcc >=3.4. You might want to wait before continuing with your porting efforts.

A Couple more errors that i have come across include "DEFFILEMODE",
"SEEK_CUR", and "ALLPERMS" aren't declared. Im actually thinking
maybe
theres a missing include dir or something...

This is very well possible and will probably be fixed after I've attacked the build system with a host gcc 4.

(Also, Really sorry for no Patches + lame probs, im still 
learning)

Regarding patches, "svn diff" works quite well. :-)

CU, Ingo

Other related posts: