This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: building cygwin.dll instructions

On Thu, Apr 12, 2001 at 12:37:24PM +1000, Robert Collins wrote:
>----- Original Message -----
>From: "Christopher Faylor" <>
>To: <>
>Sent: Thursday, April 12, 2001 12:16 PM
>Subject: Re: building cygwin.dll instructions
>> On Thu, Apr 12, 2001 at 11:36:27AM +1000, Robert Collins wrote:
>> >Can I suggest that the use of --prefix be documented? I mistakenly
>> >used --prefix=/usr and trashed my system a month or so ago - I just
>> >realised I never suggested it be documented. Something along the
>> >of
>> >
>> >"Don't use a --prefix that refers to the final destination. Use
>> >a --prefix like "/usr/src/installcygwin" and from there take the
>> >to your actual working directories."
>> Actually, I have the opposite advice.  *Always* configure with the
>> correct final destination.  You don't know what will get compiled into
>> your applications otherwise.
>> When I am building my applications, I use something like:
>> configure --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc \
>>           --libdir=/usr/lib --libexecdir=/usr/sbin
>> make
>> make prefix=/netrel/inst/usr exec_prefix=/netrel/inst/usr \
>>      sysconfdir=/netrel/inst/etc libdir=/netrel/inst/usr/lib \
>>      libexecdir=/netrel/inst/usr/sbin install
>This is precisely the knowledge I was missing when I started - and what
>IMO should be on the appropriate web page (contrib from memory).

Yes, it should be documented.  We probably need to break out the
Contributing portion of the Cygwin web page into a "Contributing to
the Cygwin core" and "Contributing an application".

One reason that I haven't done this is that I keep meaning to make my
super-wonderful automatic, drop in a package and it builds, installation
system available. (Earnie bugs me about this every time I mention it)

I have a grand plan of making a cygwin-apps repository available where
people could kick off builds on which would
eventually be automatically placed in the correct location.  I was
planning on checking in my 'mknetrel' package into that.  It's just
a large shell-script hack but it works pretty well.

Unfortunately, hard disk problems on, compounded with
recent network snafus* have kept me from implementing my goal.

I'd also love to have a web-based contribution system which would allow
people to submit their tar balls, write up a cygwin-announce blurb, and
forward the info to corinna and me for review.  Anyone want to take a
shot at that?  I'll send you a nifty Cygwin tee-shirt if you can implement
something like this.


*Someone sent a 15MB attachment to the 584 member ecos-discuss mailing list
resulting in massive network slowdowns.

Want to unsubscribe from this list?
Check out:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]