I'm lost - trying to use gcc with specs file in Windows

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

I'm lost - trying to use gcc with specs file in Windows

David Eaton
I seem to have run into what I believe is a limit to the length of a line in a .bat file (or the command line) while trying to include the libraries for building a libusb and gtk application.  As such, I looked on the internet and a site showed how to put the include libraries in the cpp area with -Ixxxxx.  I put each of the libs with a -I before it all on that one single line - it's over 256 characters long - is this a problem when the file is processed?

Also, using a very simple test program (not really a program, but used to test the includes) in C, it does not appear to picking up the -I paths as my #include <xxx> fail.

I also saw on this same internet page where to place the link libraries.  I have no idea if this is right or not since it never gets to a link.

Below is the .bat file I use in Windows at the command line:

echo off
echo *****************************************************
echo *   Build the Windows version of cvsutil for the    *
echo *   GTK gui'd interface.                            *
echo *****************************************************
echo *
echo *
echo * Creating temporary directory
echo *
mkdir dwex
echo *
echo * Beginning copies....
copy *.c_gtk dwex\*.c
copy ..\common\*.* dwex\*.*
copy windows_build_gtk_msys.sh dwex\windows_build_gtk_msys.sh
echo *
copy gccspecs dwex\gccspecs
echo * Copies completed.
cd dwex
echo *
gcc a_start.c -o c:/cvs/cvsgtk -I -specs=../gccspecs
if errorlevel == 0 goto goodbuild
if errorlevel == 1 goto goodbuilw
echo *
echo *****  the program did *NOT* build  ********
echo *
goto exitme
:goodbuild
echo *
echo *      BUILD SUCCESSFUL!!
echo *
goto exitme
:goodbuilw
echo *
echo *    Build completed with warnings
echo *
:exitme
echo *
echo Begin clean-up
echo *
del *.* /Q
echo *
echo *
echo *    removing temp directory
echo *
cd ..
rmdir dwex /Q
echo *
echo ****************************************************
echo *    Build is now finished. Press any key to       *
echo *    close this window.                            *
echo ****************************************************
pause


Below are the contents of the gccspecs:

*asm:


*asm_debug:
%{gdwarf-2*:--gdwarf2}%{!gdwarf-2*:%{g*:--gstabs}}

*asm_final:


*asm_options:
%a %Y %{c:%W{o*}%{!o*:-o %w%b%O}}%{!c:-o %d%w%u%O}

*invoke_as:
%{!S:-o %|.s |
as %(asm_options) %m.s %A }

*cpp:
%{posix:-D_POSIX_SOURCE} %{mthreads:-D_MT} -Ic:/Progra~1/LibUSB-Win32-0.1.10.1/include -Ic:/gtk/include/gtk-2.0 -Ic:/gtk/lib/gtk-2.0/include -Ic:/gtk/include/atk-1.0 -Ic:/gtk/include/cairo -Ic:/gtk/include/pango-1.0 -Ic:/gtk/include/glib-2.0 -Ic:/gtk/lib/glib-2.0/include -Ic:/gtk/include/libpng12

*cpp_options:
%(cpp_unique_options) %1 %{m*} %{std*&ansi&trigraphs} %{W*&pedantic*} %{w} %{f*} %{g*:%{!g0:%{!fno-working-directory:-fworking-directory}}} %{O*} %{undef}

*cpp_debug_options:
%{d*}

*cpp_unique_options:
%{C|CC:%{!E:%eGCC does not support -C or -CC without -E}} %{!Q:-quiet} %{nostdinc*} %{C} %{CC} %{v} %{I*} %{P} %I %{MD:-MD %{!o:%b.d}%{o*:%.d%*}} %{MMD:-MMD %{!o:%b.d}%{o*:%.d%*}} %{M} %{MM} %{MF*} %{MG} %{MP} %{MQ*} %{MT*} %{!E:%{!M:%{!MM:%{MD|MMD:%{o*:-MQ %*}}}}} %{remap} %{g3:-dD} %{H} %C %{D*&U*&A*} %{i*} %Z %i %{E|M|MM:%W{o*}}

*trad_capable_cpp:
cc1 -E %{traditional|ftraditional|traditional-cpp:-traditional-cpp}

*cc1:
%(cc1_cpu)

*cc1_options:
%{pg:%{fomit-frame-pointer:%e-pg and -fomit-frame-pointer are incompatible}} %1 %{!Q:-quiet} -dumpbase %B %{d*} %{m*} %{a*} %{c|S:%{o*:-auxbase-strip %*}%{!o*:-auxbase %b}}%{!c:%{!S:-auxbase %b}} %{g*} %{O*} %{W*&pedantic*} %{w} %{std*&ansi&trigraphs} %{v:-version} %{pg:-p} %{p} %{f*} %{undef} %{Qn:-fno-ident} %{--help:--help} %{--target-help:--target-help} %{!fsyntax-only:%{S:%W{o*}%{!o*:-o %b.s}}} %{fsyntax-only:-o %j} %{-param*}

*cc1plus:


*link_gcc_c_sequence:
%G %L %G

*endfile:
%{!fno-exceptions:crtend%O%s}

*link:
%{mwindows:--subsystem windows}   %{mconsole:--subsystem console}   %{shared: %{mdll: %eshared and mdll are not compatible}}   %{shared: --shared} %{mdll:--dll}   %{static:-Bstatic} %{!static:-Bdynamic}   %{shared|mdll: -e _DllMainCRTStartup@12 --enable-auto-image-base}

*lib:
%{pg:-lgmon} %{mwindows:-lgdi32 -lcomdlg32}                   -luser32 -lkernel32 -ladvapi32 -lshell32

*libgcc:
%{mthreads:-lmingwthrd} -lmingw32 -lgcc -lmoldname -lmingwex -lmsvcrt

*startfile:
%{shared|mdll:dllcrt2%O%s}   %{!shared:%{!mdll:crt2%O%s}} %{pg:gcrt2%O%s}    %{!fno-exceptions:crtbegin%O%s}

*switches_need_spaces:


*cross_compile:
0

*version:
3.4.5

*multilib:
. ;

*multilib_defaults:


*multilib_extra:


*multilib_matches:


*multilib_exclusions:


*multilib_options:


*linker:
collect2

*link_libgcc:
%D -lc:/gtk/lib -lc:/Progra~1/LibUSB-Win32-0.1.10.1/lib/gcc -lusb -lgtk-win32-2.0 -lgdk-win32-2.0 -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangowin32-1.0 -lgdi32 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl  

*md_exec_prefix:


*md_startfile_prefix:
/mingw/lib/

*md_startfile_prefix_1:


*startfile_prefix_spec:


*sysroot_suffix_spec:


*sysroot_hdrs_suffix_spec:


*cc1_cpu:
%{!mtune*: %{m386:mtune=i386 %n`-m386' is deprecated. Use `-march=i386' or `-mtune=i386' instead.
} %{m486:-mtune=i486 %n`-m486' is deprecated. Use `-march=i486' or `-mtune=i486' instead.
} %{mpentium:-mtune=pentium %n`-mpentium' is deprecated. Use `-march=pentium' or `-mtune=pentium' instead.
} %{mpentiumpro:-mtune=pentiumpro %n`-mpentiumpro' is deprecated. Use `-march=pentiumpro' or `-mtune=pentiumpro' instead.
} %{mcpu=*:-mtune=%* %n`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
}} %<mcpu=* %{mpni:-msse3 %n`-mpni' is deprecated. Use `-msse3' instead.
} %{mno-pni:-mno-sse3 %n`-mno-pni' is deprecated. Use `-mno-sse3' instead.
} %{mintel-syntax:-masm=intel %n`-mintel-syntax' is deprecated. Use `-masm=intel' instead.
} %{mno-intel-syntax:-masm=att %n`-mno-intel-syntax' is deprecated. Use `-masm=att' instead.
}

*mingw_include_path:
mingw32

*link_command:
%{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S:    %(linker) %l %{pie:-pie} %X %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} %{r}    %{s} %{t} %{u*} %{x} %{z} %{Z} %{!A:%{!nostdlib:%{!nostartfiles:%S}}}    %{static:} %{L*} %(link_libgcc) %o %{fprofile-arcs|fprofile-generate:-lgcov}    %{!nostdlib:%{!nodefaultlibs:%(link_gcc_c_sequence)}}    %{!A:%{!nostdlib:%{!nostartfiles:%E}}} %{T*} }}}}}}


I have tried searching the web, reading all kinds of sites, etc., and am lost.  I don't understand what the specs file stuff actually means (I've read the descriptors, but I don't understand how they get parsed out).  I am at a loss to understand why the includes (usb.h and gtk.h so far) are not found. The output from the batch file when it gets to the gcc line says that usb.h and gtk.h are not found.

I need all kinds of help and am begging someone to help me with this.  I used to have `pgk-config --gtk+-2.0` on the gcc line in a shell script and paused the batch file to tell the user to go to msys and run the script, then come back and press enter.  It worked, but how clumsy!  I thought I should be able to build something that will just run in the batch file itself.  In this way I can automate installation and compilation.  But right now I'm really stuck.

Thank you for reading this and thanks in advance for any help!

Dave




     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

Tuomo Latto
David Eaton wrote:
> I seem to have run into what I believe is a limit to the length of a line in a .bat file (or the command line) while trying to include the libraries for building a libusb and gtk application.  As such, I looked on the internet and a site showed how to put the include libraries in the cpp area with -Ixxxxx.  I put each of the libs with a -I before it all on that one single line - it's over 256 characters long - is this a problem when the file is processed?
>
> Also, using a very simple test program (not really a program, but used to test the includes) in C, it does not appear to picking up the -I paths as my #include <xxx> fail.
>
> I also saw on this same internet page where to place the link libraries.  I have no idea if this is right or not since it never gets to a link.

First of all, how about putting in some line breaks?

Second, you are using a specs file but don't know the
difference between a header and a library?
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.

>From what I can tell, you should read up on compiling C
and libraries, etc:
http://www.cs.cf.ac.uk/Dave/C/node3.html
http://www.cs.cf.ac.uk/Dave/C/node35.html#ch:prog
http://www.cs.cf.ac.uk/Dave/C/node3.html#SECTION00326000000000000000

...and see GCC manual:
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/

...and maybe find out about make and Makefiles.


--
Tuomo

... Point not found. A)bort, R)eread, I)gnore


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

David Eaton



--- On Sat, 1/31/09, Tuomo Latto <[hidden email]> wrote:

> From: Tuomo Latto <[hidden email]>
> Subject: Re: [Mingw-users] I'm lost - trying to use gcc with specs file in Windows
> To: "MinGW Users List" <[hidden email]>
> Date: Saturday, January 31, 2009, 5:30 AM
> David Eaton wrote:
> > I seem to have run into what I believe is a limit to
> the length of a line in a .bat file (or the command line)
> while trying to include the libraries for building a libusb
> and gtk application.  As such, I looked on the internet and
> a site showed how to put the include libraries in the cpp
> area with -Ixxxxx.  I put each of the libs with a -I before
> it all on that one single line - it's over 256
> characters long - is this a problem when the file is
> processed?
> >
> > Also, using a very simple test program (not really a
> program, but used to test the includes) in C, it does not
> appear to picking up the -I paths as my #include <xxx>
> fail.
> >
> > I also saw on this same internet page where to place
> the link libraries.  I have no idea if this is right or not
> since it never gets to a link.
>
> First of all, how about putting in some line breaks?
>
> Second, you are using a specs file but don't know the
> difference between a header and a library?
> 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.
>
> >From what I can tell, you should read up on compiling C
> and libraries, etc:
> http://www.cs.cf.ac.uk/Dave/C/node3.html
> http://www.cs.cf.ac.uk/Dave/C/node35.html#ch:prog
> http://www.cs.cf.ac.uk/Dave/C/node3.html#SECTION00326000000000000000
>
> ...and see GCC manual:
> http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/
>
> ...and maybe find out about make and Makefiles.
>
>
> --
> Tuomo
>
> ... Point not found. A)bort, R)eread, I)gnore
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> MinGW-users mailing list
> [hidden email]
>
> You may change your MinGW Account Options or unsubscribe
> at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
>
> _______________________________________________
> This list observes the Etiquette found at
> http://www.mingw.org/Mailing_Lists.
> We ask that you be polite and do the same.
>
> Most annoying abuses are:
> 1) Top posting
> 2) HTML/MIME encoded mail
> 3) Improper quoting
> 4) Improper trimming

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.

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.

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.


     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

David Eaton
In reply to this post by Tuomo Latto
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.


--- On Sat, 1/31/09, Tuomo Latto <[hidden email]> wrote:

> From: Tuomo Latto <[hidden email]>
> Subject: Re: [Mingw-users] I'm lost - trying to use gcc with specs file in Windows
> To: "MinGW Users List" <[hidden email]>
> Date: Saturday, January 31, 2009, 5:30 AM
> David Eaton wrote:
> > I seem to have run into what I believe is a limit to
> the length of a line in a .bat file (or the command line)
> while trying to include the libraries for building a libusb
> and gtk application.  As such, I looked on the internet and
> a site showed how to put the include libraries in the cpp
> area with -Ixxxxx.  I put each of the libs with a -I before
> it all on that one single line - it's over 256
> characters long - is this a problem when the file is
> processed?
> >
> > Also, using a very simple test program (not really a
> program, but used to test the includes) in C, it does not
> appear to picking up the -I paths as my #include <xxx>
> fail.
> >
> > I also saw on this same internet page where to place
> the link libraries.  I have no idea if this is right or not
> since it never gets to a link.
>
> First of all, how about putting in some line breaks?
>
> Second, you are using a specs file but don't know the
> difference between a header and a library?
> 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.
>
> >From what I can tell, you should read up on compiling C
> and libraries, etc:
> http://www.cs.cf.ac.uk/Dave/C/node3.html
> http://www.cs.cf.ac.uk/Dave/C/node35.html#ch:prog
> http://www.cs.cf.ac.uk/Dave/C/node3.html#SECTION00326000000000000000
>
> ...and see GCC manual:
> http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/
>
> ...and maybe find out about make and Makefiles.
>
>
> --
> Tuomo
>
> ... Point not found. A)bort, R)eread, I)gnore
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> MinGW-users mailing list
> [hidden email]
>
> You may change your MinGW Account Options or unsubscribe
> at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
>
> _______________________________________________
> This list observes the Etiquette found at
> http://www.mingw.org/Mailing_Lists.
> We ask that you be polite and do the same.
>
> Most annoying abuses are:
> 1) Top posting
> 2) HTML/MIME encoded mail
> 3) Improper quoting
> 4) Improper trimming


     

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

Tuomo Latto
In reply to this post by David Eaton
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!


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

Guido De Rosa
In reply to this post by David Eaton
Seems like you searched the wrong keywords on the web...

I'd suggest you to use Makefiles instead of MSDOS batch files; and
probably you don't need to handle specs files.

Makefiles may be written by hand, but it's common creating them
automatically: the traditional approach requires GNU
autoconf/automake, but it's complicated. A more user-friendly way is
given by CMake.

For example, searching "cmake gtk mingw" I get something like this:

http://www.k-3d.org/wiki/Windows_Build/MinGW

Maybe you can use the build process of this application as a template
for yours...

HTH
Guido

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

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

Keith Marshall
In reply to this post by David Eaton
On Saturday 31 January 2009 14:23:28 David Eaton wrote:
> 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.

David,

I am sorry that you have had an unpleasant experience of seeking help
on this list, and that you are discouraged from using MinGW and MSYS
as a result.  We *do* aim to provide support for *all* users, with
*any* level of experience, novice to expert.

As list moderator, I do try to read all posts; I found yours rather
uncomfortable to read, and that "discomfort factor" may go some way
to explain the lack of an encouraging response.  I do hope that you
may be persuaded to persevere, and put this bad experience behind
you.  Here are some tips, to help you avoid the grief:

1) Set up your mail client, or whatever editor it uses to compose
messages, to post in plain text only, (as you did; this wasn't your
problem), and to *fold* the text you *type*, (not files you copy and
paste), at a line length of between 65 and 72 characters.  (This
*was* your problem; your text sprawled all the way across the screen.  
This makes it uncomfortable to read, and difficult to quote in reply;
many readers will simply abandon you after two or three lines, and
the most likely to do so are the experts you are hoping might give
you a helpful answer to your question).

2) Ask your question clearly and concisely, but be sure to include
sufficient detail to show us what you are trying to achieve, how you
are trying to achieve it, what outcome you expect, and what is not
working as you expect it to.  (This is where it is important to copy
and paste actual commands and resultant diagnostics).

3) If you do receive what you consider to be an offensive response,
just ignore it; say that you don't understand what the offensive
poster was trying to tell you, and hope that someone else will be
more helpful.

4) Read Eric Raymond's and Rick Moen's advice on "asking questions the
smart way": http://www.catb.org/~esr/faqs/smart-questions.html


And finally...

To answer your original question: you shouldn't be using the GCC specs
file to achieve your goal.  Neither should you really be resorting to
cmd.exe's batch files to supplant "make"; they are not well suited to
this purpose, and some would call you an extreme masochist for even
considering this approach.  Use MSYS to host your build environment,
and learn to use "make"; it will provide a much more pleasant user
experience, and will pay dividends in the long term; (FWIW, I have
never encountered a command line length limit using these tools --
yes, there is one, but it is usually more than sufficient).

--

Regards,
Keith.

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming