Hi Chuck,
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any non-museum Windows compiler
that would break if I removed it?
Here's what I'm proposing to do for
Gary V. Vaughan skrev 2011-10-25 12:51:
Hi Chuck,
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any non-museum Windows compiler
that would break if I
Hi Peter,
On 25 Oct 2011, at 18:12, Peter Rosin wrote:
Gary V. Vaughan skrev 2011-10-25 12:51:
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any
On Tue, 25 Oct 2011, Gary V. Vaughan wrote:
Hi Chuck,
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any non-museum Windows compiler
that would break if I
On 10/25/2011 6:51 AM, Gary V. Vaughan wrote:
Do you forsee any issues on Windows with my doing that?
Yes.
I'm almost certain that modern gcc and hence cygwin and variants will
continue to work correctly without LT_SCOPE, LTDL_DLL_IMPORT and friends,
but I have no clue whether vendor
Bob Friesenhahn skrev 2011-10-25 16:00:
On Tue, 25 Oct 2011, Gary V. Vaughan wrote:
Hi Chuck,
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any
Gary V. Vaughan skrev 2011-10-25 14:17:
Hi Peter,
On 25 Oct 2011, at 18:12, Peter Rosin wrote:
Gary V. Vaughan skrev 2011-10-25 12:51:
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of
On 10/25/2011 11:03 AM, Peter Rosin wrote:
Gary V. Vaughan skrev 2011-10-25 14:17:
I configures both the way I usually configure libtool for msvc, i.e.
../configure autobuild_mode=msvc CC=/c/cygwin/home/peda/automake/lib/compile
cl CFLAGS=-MD -Zi -EHsc
Hi Peter, Bob, Chuck,
Thanks all for the feedback.
And Peter especially for running the torturous testsuites on Windows :)
On 25 Oct 2011, at 21:34, Peter Rosin wrote:
Bob Friesenhahn skrev 2011-10-25 16:00:
On Tue, 25 Oct 2011, Gary V. Vaughan wrote:
I note that no other GNU projects that
I should also add:
On 25 Oct 2011, at 21:34, Peter Rosin wrote:
Bob Friesenhahn skrev 2011-10-25 16:00:
On Tue, 25 Oct 2011, Gary V. Vaughan wrote:
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Gary V. Vaughan skrev 2011-10-25 18:07:
I should also add:
On 25 Oct 2011, at 21:34, Peter Rosin wrote:
Bob Friesenhahn skrev 2011-10-25 16:00:
On Tue, 25 Oct 2011, Gary V. Vaughan wrote:
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the
Charles Wilson skrev 2011-10-25 17:34:
On 10/25/2011 11:03 AM, Peter Rosin wrote:
Gary V. Vaughan skrev 2011-10-25 14:17:
I configures both the way I usually configure libtool for msvc, i.e.
../configure autobuild_mode=msvc
CC=/c/cygwin/home/peda/automake/lib/compile cl CFLAGS=-MD -Zi -EHsc
Hi Gary,
Gary V. Vaughan wrote:
Hi Chuck,
I note that no other GNU projects that I'm aware of jump through all the
__declspec hoops that the libltdl API tries to provide through LT_SCOPE.
Is any of this stuff still required on any non-museum Windows compiler
that would break if I removed it?
On 10/25/2011 11:51 AM, Gary V. Vaughan wrote:
I have to bow to your superior knowledge of Windows, which I haven't used
for development since Windows NT 4, but it feels weird that Libltdl really
does twist itself into a pretzel for Windows... and yet all the other GNU
projects I've looked at do
14 matches
Mail list logo
