Re: [Mingw-users] I'm lost - trying to use gcc with specs file in Windows

[Tuomo L. <dj...@ik...>]

Re-arranged somewhat..

David Eaton wrote:
>> First of all, how about putting in some line breaks?
> 
> I copied and pasted the file - I didn't want to add extra line feeds when they weren't in the file.  I already stated why I'm using the specs file - the cli in Windows has a limit to the number of characters on each line, and since it doesn't do the `pkg-config --gtk+-2.0` expansion, I had to specify each of the libraries, and this made the line WAY over 256 bytes.

I mean your e-mails. It looks as if your mailer thinks line
breaks should only be used as paragraph separators. The text
is difficult to read and very annoying to quote as it gets
messed up - especially with multiple levels of quotation.


>> Second, you are using a specs file but don't know the
>> difference between a header and a library?

This quote from another mail:
> And, while technically a library is a "compiled" collection in a single file, I use the term loosly to also refer to a directory containing many pieces of code to be use in #include for headers or otherwise for pieces of code to be copied into the current code.  I do quite well know the difference between a header and a library.

There are people who don't know the difference between
the two and are suprised to find out about it. I've even seen
it on this very list.
Using the term loosely very much makes you look like one of them
since you mix two separate key terms "include" and "library".
Anyway, since you know the difference, then you probably also
know that an "include library" is simply one or more source
files and the difference to us or the compiler is largely cosmetic
and only serves to confuse the issue.


>> Why are you using a specs file?
>> It's usually a good idea to know why you're doing
>> something
>> before you actually do it.
> 
> As I mentioned, I've read everything I could, and as I mentioned I'm lost.  As mentioned, I found a web site that said to gcc -dumpspecs > filename to create the basic specs file.  It showed where to put the include libraries - which from what I understand are any source library to which a #include statement is issued.  I also ran a pkg-config with gtk+-2.0 and piped the output to another file.  I used that file to also include the libraries needed since I was using GTK.  As mentioned, I placed the link libraries - at least that's what I understood -llibname to be - in the section of the specs file according to the website I referenced.
> 
> I may be extremely ignorant of this whole process, and I thought I made that very clear in my post - so why jump on me about it?  Can't you just say "we can't help you here" or some such thing?
> 
> BTW - just so you know I'm not a complete fool - I changed the batch file to execute msys with the shell script so I only need the batch file now, no extra script, and I don't need the specs file since msys does the `pkg-config --gtk+-2.0` expansion and substitution.
> 
> I'm sorry that every time I get on this and explain up front that I'm a beginner and don't know what I'm doing that everyone seems to want to jump on me.  I'm just ignorant, NOT stupid, and don't understand this mentality.  If you don't want people asking how to use the product, then I guess you want to keep it to yourselves instead of making it available to the world as you do.  If it really ticks you off, start a beginners list, expecting ignorant questions there and hopefully providing help.
> 
> Personally, all I've done is asked for beginners help and thought ignorance would be tolerated - stupidity no, ignorance God yes.  I guess I've been wrong on both accounts.  The only way of contacting people that I found on the pages at sourceforge.net for these projects was via this subscription list.  I assumed that meant for *ANY* questions and problems, not things about the internals. Believe it or not - doesn't matter to me - I was a systems programmer for over 20 years, and I know the difference between someone asking me a question out of ignorance [used to mean lack of knowledge] versus stupidity [meaning they couldn't understand no matter what].  If this list is supposed to be about the internals and not for "users", then the list name is misleading and another means of support needs to be offered.
> 
> Try looking on the web sometime for Windows gcc pkg-config - you'll be suprised what you DON"T get.  Try the same thing for Windows gcc specs file line length limit - you get bupkus.  I know how to search the web, I know how to read, and I know how to interpret.  Forgive me if you think that makes me a fool.

I seem to have forgotten to answer your initial question
concerning the command-line length. For that I apologize:
http://www.google.com/search?q=%2Bwindows+%2B%22command-line%22+%2Blength
The second result may be (may have been?) helpful.


Regarding your real or perceived stupidity, ignorance, or lack of
either or both, all I have to work with is your postings.
I've taken a curious habit *not* to search the archives or the web for
every single poster in order to deduce their skill level or other
personal traits or information about them. I don't know your background!
However, you seemingly mixing libraries with header files made you look
like someone who doesn't know what he is doing and shouldn't be messing
with specs files. Especially since you insist on calling yourself a beginner.
Whether ignorant or stupid, I don't know or really care.
Should that really make a difference?

I didn't tell you "we can't help you here" simply because that would have
been untrue. Your problem *seemed* to be a lack of understanding concerning
the compilation process and helping with that here isn't about "can't" but
"won't" and "shouldn't".
Concerning the actual problem, the use of different command-line interpreter
(essentially MSYS), changing to use shorter paths (moving stuff around
or using junction) or building things in stages (intermediate libraries, etc)
would have also helped. Someone might have eventually suggested using
pkg-config as well, but that only works around the CLI limitation
(not the OS one) and I'm not sure MSYS even has one. (Has it? Anyone?)

I also feel compelled to point out that you didn't show the failing
command-line but instead gave us a simplified example of something
*not actually showing the problem* (also featuring that cool
empty -I parameter).
That won't help anyone come up with suggestions.


> With these types of responses from both of my posts, I plan not to use mingw or msys again and find another means for cross-platform compilation.  I don't need the grief - just answers.

I could say something like that myself..
You are of course free to use whatever tools you want.


Oh, what's with the Reply-To? Aren't you subscribed?

-- 
Tuomo

... Save the planet, kill the people!