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

Mathew Schofield <mr.skoe@xxxxxxxxx> wrote:
> Hi again!
> Before i get started playing around with a Cirrus VGA Graphics 
> driver,
> and an IRC Client for Haiku, i would love to be able to compile Haiku

May I just express my curiosity what's up with all those IRC clients? 
BeOS does already have plenty of them - even though Vision is not only 
one of the latest but also the best clients, is it really necessary to 
waste energy on a new client?
Vision will run on Haiku just fine (as will all the other BeOS IRC 
clients - that ran fine on BeOS :-)).

> 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 
> ;;"]
> 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).

> 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>?

> 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...

As the missing ECANCELED I would think this is either a bug in your 
configuration or Cygwin. If possible, this should be fixed where the 
bug is, and not worked around somewhere else.

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

No problem, you're welcome :-)
I don't think building on Windows has a high priority, but if you 
manage to do that cleanly, why not.

> Also a non-windows related thing,
> Running terminal within Terminal (ie. cd-ing to the bin dir and
> running termainl) caused segment violation. (Just thought id mention
> it...)
>       "0x0025d01b in ServerWindow::SendMessageToClient ()"

Works fine over here.

Bye,
   Axel.

Other related posts: