Mail Archives: cygwin/2004/04/08/14:20:03
On Thu, 8 Apr 2004, Christopher Faylor wrote:
> On Thu, Apr 08, 2004 at 10:00:56AM -0700, Peter A. Castro wrote:
> >The @filename syntax is used by MS's linker (Visual C++/Studio). To my
> >knowledge gcc's linker doesn't support this syntax.
>
> The cygwin DLL supports it (implemented over my gagged and thrashing body)
> but only at a non-cygwin-shell command prompt, e.g.,
Good Gravy!! Yikes!! *Tell me* this is a late April Fool's joke!! Please!!
> c:\>gcc -o foo @foo.blah
>
> works
>
> but
>
> bash$ gcc -o foo @foo.blah
>
> doesn't.
>
> I would highly recommend against using this construct, however. It's better
> to use traditional unix methods for working around this problem. Cygwin isn't
> the only unix-like system out there with a measly amount of space set aside for
> the command line.
The original post doesn't specify weither they are working inside of or
outside of a Cygwin environment, but from some of the comments I kinda
think it maybe outside of. Something like:
On Thu, 8 Apr 2004, Johan Holmberg wrote:
> Is ld.exe not interpreting the special "@" like other
> Cygwin programs ?
Kinda makes me think he's running this from outside of any Cygwin shell.
But, my original suggestion, as well as your mention above, still stands:
use traditional unix methods, like static-link archive libraries.
Related to, but just as problematic, would be turning all of those object
files into a shared-library/DLL, which I encourage the original poster to
also consider if this program is ment to be run concurrently.
> cgf
--
Peter A. Castro <doctor AT fruitbat DOT org> or <Peter DOT Castro AT oracle DOT com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -