Charles Wilson [EMAIL PROTECTED] writes:
Well, as I described in the other message, there are only three
patches.
Ok, I must have looked over it.
One, which creates a Makefile.config,
Two, a cygwin-specific README file.
Three, GNU shtool, to create a shadow tree in which to build.
With the ability to generate -src snapshots, I can now make setup.exe
-src tarballs easily. I'd like to package up a -src only package with
the current released setup sources in 'curr', and (possibly) any new
versions in 'test'. For now I don't intend to offer binary packages,
because setup
Tie ago I tried bitkeeper... it's installer is very neat and works very
well and uses cygwin in the right way... only it has a problem I've
already reported in their bug management ssytem (it thinks cygwin it's
installed in c:\cygwin\ also if I skipped installing it as I already had
it in a
To detect cygwin's location, you should link against cygwin, and use
pathconv to get the location of /.
Rob
Ok, I see what it does. Doesn't it have to do that for each reference to
the auto-imported variable?
For each auto-imported variable an IMAGE_IMPORT_DESCRIPTOR and an
IMPORT_THUNK_DATA element is necessary.
If so, then heavy use of an imported variable could make the
INT and IAT quite large
Gary R. Van Sickle wrote:
(thank the three men I admire most,
the Father, Son, and the Holy Ghost!).
Hah! An American Pie reference! Bye, bye Miss American Pie, Drove my
chevy to the levy but the levy was dry...
--Chuck
-Original Message-
From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 4:39 AM
It is more usual for projects to store the configure scripts,
however. It is also more usual not to change the convention
once it has been set.
And I have _not_ changed
