This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Where are Reg* implemented?
- To: <gnu-win32 at cygnus dot com>, "Justin Hopkins" <hop at elwood dot pionet dot net>
- Subject: Re: Where are Reg* implemented?
- From: "Wei Ku" <weiku at UTKUX1 dot UTK dot EDU>
- Date: Thu, 31 Jul 1997 23:03:04 -0400
My impression ( an what I always do ) is to put the options before the
files to be compiled or linked as following:
g++ -o outfilename -O -L libpath -l lib file.c file.o ...
Sincerely,
Wei Ku
***************************************
Department of Physics and Astronomy
The University of Tennessee
1408 Circle Drive
Knoxville, Tennessee 37996-1200
weiku@utkux.utcc.utk.edu
---------------------------------------
Solid State Division
Oak Ridge National Laboratory
P.O.Box 2008
Oak Ridge, TN 37831-6032
Phone: (423) 574-5795
Fax: (423) 574-4143
weiku@solid.ssd.ornl.gov
***************************************
-----Original Message-----
From: Justin Hopkins <hop@elwood.pionet.net>
To: gnu-win32@cygnus.com <gnu-win32@cygnus.com>
Date: Thursday, July 31, 1997 10:27 PM
Subject: Re: Where are Reg* implemented?
>At 01:08 AM 7/31/97 +0100, you wrote:
>>I copied this testprogram from the M$ manuals, which uses
>>the RegOpenKeyExA, RegQueryValueExA, RegQueryInfoKeyA and
>>RegCloseKey functions. They are defined in windows.h, and
>>a quick "strings -f *.a | grep Reg" finds the symbols in
>>libadvapi32.a
>>
>>gcc -ladvapi32 pdh.c -o pdh
>
>
>Try using this command-line>
> gcc -o pdh.exe pdh.c -ladvapi32
>
>I may be wrong, but I think gcc/g++ expect your libraries
>to be at the end of the command line invocation.
>
>Justin Hopkins
>
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".