Re: Building the cygwin.dll for other architectures

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

----- Original Message -----
From: "Jacob Hansen" <luffe@diku.dk>
To: <cygwin@cygwin.com>
Sent: Tuesday, October 02, 2001 10:40 PM
Subject: Building the cygwin.dll for other architectures


> Hi,
>
> I am using an embedded OS named Pharlap ETS. This OS uses Win32 API.
The
> development environment is Visual C++ and a custom linker (called
LINKLOC).
>
> How would I go about building the cygwin.dll for this arch, so I can
link my
> apps to it? The reason being that I would like to use SAMBA on this
> platform.

Start by creating gcc target support for Pharlap ETS. This will involve
(at a minimum) creating ld capability to replace LINKLOC. ALlow 6-8
weeks (rough guess) to get it going. A good gcc hacker with appropriate
doco available might do it faster - but you'd have to motivate them
somehow. (This list is not appropriate for this step - gcc has it's own
lists).

Then _port_ cygwin to Pharlap ETS. This will involve adding code to
cygwin to handle any platform differences between (pick one)
NT4/2k/me/9x and Pharlap ETS. Then you should be able to create a
cross-compiled cygwin. Now run the test suite within Pharlap ETS.
Iterate on this point until no failures occur on Pharlap that do not
occur under NT. If Pharlap is _identical_ (and the presence of a custom
linker does _not_ fill me with confidence) then this should be trivial.

Now you can begin work on samba.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/