This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: setup: use external crypto libraries
On Thu, Mar 25, 2010 at 10:05:51AM -0400, Charles Wilson wrote:
>On 3/18/2010 8:40 PM, Charles Wilson wrote:
>> Here's the promised patch. You need to install
>> mingw-libgpg-error-devel and
>> mingw-libgcrypt-devel
>> and re-run bootstrap.sh in both setup's src dir and the libgetopt++ subdir.
>>
>> 2010-03-18 Charles Wilson <...>
>>
>> Use external crypto libraries
>> * Makefile.am: Remove local libgcrypt and libgpg-error
>> source directories from AM_CPPFLAGS.
>> * configure.ac: Remove libgcrypt and libgpg-error subdirs
>> from AC_CONFIG_SUBDIRS. Remove now-unnecessary cruft.
>> * doconfigure: Specify gcc-3 and g++-3. Set PATH when $build
>> is cygwin, so that correct (mingw) libgcrypt and libgpg-error
>> config scripts can be used.
>
>Ping?
>
>Especially: cgf, can you test this patch in your cross-build
>environment, with the two mingw-* libraries installed, and verify that
>IN that environment, you are still able to build a setup.exe that does
>not have a non-empty .tls section? I'm pretty sure that will be the
>case, but a little verification wouldn't hurt.
It doesn't matter. If it works in the native environment, I'll make
it work in the cross environment.
I'd rather get verification that it works in the native environment
for someone else.
(And, you just *know* that someone in the cygwin list will start
complaining because "setup no longer builds" shortly after this change
is checked in)
>Hmmm...now that I think about it, what do you think about the
>doconfigure changes, cgf?
I don't use doconfigure but it surely is not now nor has it ever been
cross-compile friendly. I don't even think it should be in the
checked in.
cgf