On Thu, Nov 22, 2012 at 4:07 AM, JonY wrote:
>
> See gcc -print-search-dirs, usually in
> $prefix/[x86_64-w64-]mingw32/include and it's sibling lib or lib64 dirs.
>
Or it might be lib or lib32 directories. The TDM distribution puts
the 64bit in lib and 32bit in lib32.
--
Earnie
-- https://sites
Hi,
the environment variables LIBRARY_PATH, C_INCLUDE_PATH, and
CPLUS_INCLUDE_PATH might be of some help here to you. You can find in
gcc's documentation some further information about those (and some
more) environment variables.
Regards,
Kai
On 11/22/2012 01:53, Baruch Burstein wrote:
> Where would I place files for additional libraries I want to always be
> available for `#include`ing and `-l`inking? For example boots headers and
> libraries, or zlib.h and libz.a.
>
> I am using Ruben's 64->64 compiler setup.
>
See gcc -print-searc
I am not using MSYS.
On Thu, Nov 22, 2012 at 12:56 AM, deneme.true wrote:
> Hello,
>
> Baruch,
>
> I am using similar to this configuration at indicated this article:
> http://ingar.satgnu.net/devenv/mingw32/base.html
>
> I can easily change Mingw32 to Ming64 with:
> for Mingw32:
> source /local
Hello,
Baruch,
I am using similar to this configuration at indicated this article:
http://ingar.satgnu.net/devenv/mingw32/base.html
I can easily change Mingw32 to Ming64 with:
for Mingw32:
source /local32/etc/profile.local
for Mingw64:
source /local64/etc/profile.local
and libraries and program
Where would I place files for additional libraries I want to always be
available for `#include`ing and `-l`inking? For example boots headers and
libraries, or zlib.h and libz.a.
I am using Ruben's 64->64 compiler setup.
--
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
--
