RE: Visual Studio linking

2004-12-17 Thread Larry Hall
At 04:36 PM 12/17/2004, you wrote: >So, I realized I had the compile option "Use Managed Extensions" on in VS >.NET and that was causing the problem. Really. That was it? Well, that's pretty non-intuitive. Nice job finding that. >Now that I can include the libs in >my project, are there a

RE: Visual Studio linking

2004-12-17 Thread Daniel Starin
s or type specifiers . Thanks, Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Hall Sent: Sunday, December 12, 2004 5:51 PM To: Daniel Starin; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Visual Studio linking At 05:39 PM 12/12/2004, you wr

Re: Visual Studio linking

2004-12-12 Thread Larry Hall
At 05:39 PM 12/12/2004, you wrote: >Hi. > >I am also trying to use functions implemented in cygwin1.dll with >Visual Studio as discussed below. After started a blank console application >and following steps below, I get to linking which gives me the following >error: > >Linking... >LIBCMTD.lib

Re: Visual Studio linking

2004-12-12 Thread Daniel Starin
Hi. I am also trying to use functions implemented in cygwin1.dll with Visual Studio as discussed below. After started a blank console application and following steps below, I get to linking which gives me the following error: Linking... LIBCMTD.lib(crt0.obj) : error LNK2005: _mainCRTStar

Re: Visual Studio linking

2004-06-08 Thread Christopher Faylor
On Tue, Jun 08, 2004 at 10:02:08AM +0100, Alastair Growcott wrote: >Actually my source is testing a library, so if I did distribute the >test programs, I would only have to make the code for the test programs >and not the code for the libraries available (dynamic linking to the >libraries). As lon

RE: Visual Studio linking

2004-06-08 Thread Alastair Growcott
] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: 07 June 2004 17:25 To: [EMAIL PROTECTED] Subject: Re: Visual Studio linking On Mon, Jun 07, 2004 at 05:13:25PM +0100, Alastair Growcott wrote: >>A .def file is generated for cygwin when the DLL is built, actually. > >I'm

Re: Re[5]: Visual Studio linking

2004-06-07 Thread Joshua Daniel Franklin
On Mon, 7 Jun 2004 15:38:21 +0100 (GMT Daylight Time), Alastair Growcott wrote: > To all those who said it couldn't be done...I've done it :) I'll update the FAQ with this info. Including cgf's link to the GNU website. :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem

Re: Visual Studio linking

2004-06-07 Thread Christopher Faylor
On Mon, Jun 07, 2004 at 05:13:25PM +0100, Alastair Growcott wrote: >>A .def file is generated for cygwin when the DLL is built, actually. > >I'm not building the Cygwin dll, so I need this step. > >>5a) Modify the license of your program to the GNU General Public >>License, since your binary has no

Re[2]: Visual Studio linking

2004-06-07 Thread Alastair Growcott
> A .def file is generated for cygwin when the DLL is built, actually. I'm not building the Cygwin dll, so I need this step. > 5a) Modify the license of your program to the GNU General Public > License, since your binary has now become GPLed, meaning that you must > now offer the source code to

Re: Visual Studio linking

2004-06-07 Thread Christopher Faylor
On Mon, Jun 07, 2004 at 03:38:21PM +0100, Alastair Growcott wrote: >Seriously, it is quite easy once you figure it out, and I am sure there >are plenty of people who helped write Cygwin who probably knew but >couldn't be bothered to tell me. Well, we are all just very mean. >It involves a couple

Re[5]: Visual Studio linking

2004-06-07 Thread Alastair Growcott
To all those who said it couldn't be done...I've done it :) Hahahaha. Seriously, it is quite easy once you figure it out, and I am sure there are plenty of people who helped write Cygwin who probably knew but couldn't be bothered to tell me. It involves a couple of minor hacks. It would be nice

RE: Re[6]: Visual Studio linking

2004-06-03 Thread Hughes, Bill
> Sent: 02 June 2004 18:43 From: Christopher Faylor > On Wed, Jun 02, 2004 at 04:54:54PM +0100, Hughes, Bill wrote: > >> From: Christopher Faylor > >> On Wed, Jun 02, 2004 at 04:02:39PM +0100, Dave Korn wrote: > >> >> -Original Message- > >> >> From: Alastair Growcott > [mailto:[EMAIL PRO

RE: Re[4]: Visual Studio linking

2004-06-02 Thread Karl M
Hi Dave... Now be honest Dave...How do you really feel about this? :.) IANAT (I am not a therapist). Enjoy, ...Karl From: "Dave Korn" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: RE: Re[4]: Visual Studio linking Date: Wed, 2 Jun 2004 14:54:47 +0100 > -Ori

Re: Re[6]: Visual Studio linking

2004-06-02 Thread Christopher Faylor
On Wed, Jun 02, 2004 at 04:54:54PM +0100, Hughes, Bill wrote: >> From: Christopher Faylor >> On Wed, Jun 02, 2004 at 04:02:39PM +0100, Dave Korn wrote: >> >> -Original Message- >> >> From: Alastair Growcott [mailto:[EMAIL PROTECTED] >Ahem! ^^

RE: Re[6]: Visual Studio linking

2004-06-02 Thread Hughes, Bill
> From: Christopher Faylor > On Wed, Jun 02, 2004 at 04:02:39PM +0100, Dave Korn wrote: > >> -Original Message- > >> From: Alastair Growcott [mailto:[EMAIL PROTECTED] Ahem! ^^^ PCYMTNQREAIYR ?? Sorry, couldn't resist. (I know,

Re: Re[6]: Visual Studio linking

2004-06-02 Thread Christopher Faylor
On Wed, Jun 02, 2004 at 04:02:39PM +0100, Dave Korn wrote: >> -Original Message- >> From: Alastair Growcott [mailto:[EMAIL PROTECTED] >> Sent: 02 June 2004 15:10 >> To: Dave Korn > >[snip privately sent email] > > Please keep this discussion on the list. You don't have to take my advice

RE: Re[6]: Visual Studio linking

2004-06-02 Thread Dave Korn
> -Original Message- > From: Alastair Growcott [mailto:[EMAIL PROTECTED] > Sent: 02 June 2004 15:10 > To: Dave Korn [snip privately sent email] Please keep this discussion on the list. You don't have to take my advice if you don't want to, but you're not invited to mail me personally.

RE: Re[4]: Visual Studio linking

2004-06-02 Thread Dave Korn
> -Original Message- > From: cygwin-owner On Behalf Of Alastair Growcott > Sent: 02 June 2004 14:44 > To: cygwin > Subject: Re[4]: Visual Studio linking > > Conclusions: Real Conclusion: You are completely wasting your time in a pointless exercise of cobblin

Re[4]: Visual Studio linking

2004-06-02 Thread Alastair Growcott
Conclusions: I cannot link to a "*.a" library using the Windows linker. This is because these libraries are built with a dependency on the symbol __data_start__ which is a gcc construct. If I can figure out the correct entry point then I can link to my manufactured cygwin DLL import library wh

Re[3]: Visual Studio linking

2004-06-02 Thread Alastair Growcott
Ok, so progress so far. By the way, a main reason I am posting this stuff is so that in future anyone trying the same can search the archives and find all these posts. If anyone reads it and actually helps me, that would be a bonus :) I now have what seems to be a proper import library for cygwi

Re[2]: Visual Studio linking

2004-06-02 Thread Alastair Growcott
So far so good - not. I am trying to link against the lib*.a files using the Visual Studio linker, and it seems to accept them. However I do get the following warning; libcygwin.a(d001126.o) : warning LNK4078: multiple '.text' sections found with different attributes (E020) Moreover wh

Re: Visual Studio linking

2004-06-02 Thread Max Bowsher
Alastair Growcott wrote: > Hi. > > I have read all the FAQs and stuff. I have searched the web. I would like a > step by step list of instructions to achieve the following. > > I want to use check to test an MFC application. This means I must use the > Visual Studio compiler, cl, and linker, link.

Visual Studio linking

2004-06-02 Thread Alastair Growcott
Hi. I have read all the FAQs and stuff. I have searched the web. I would like a step by step list of instructions to achieve the following. I want to use check to test an MFC application. This means I must use the Visual Studio compiler, cl, and linker, link. Check calls fork(). This function i