|
|
Subject: Re: Re: Description of MSYS in forthcoming C++ Cookbook, by O'Reilly - msg#00040
List: gnu.mingw.msys
Keith MARSHALL wrote:
> Jonathan Turkanis wrote:
> > As I mentioned in a reply to Greg Chicares, which I just sent, my
> > problem is that command-line options using "/" are [interpreted] as
> > POSIX-paths. Some Windows tools don't allow command-line options
> > beginning with - instead of /.
>
> And for those, you type the command as "foo //option ..."; this is
> documented in the README file distributed with MSYS.
Thanks, I overlooked this.
Jonathan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: Re: Description of MSYS in forthcoming C++ Cookbook, by O'Reilly
Max T. Woodbury wrote:
> Jonathan Turkanis wrote:
>>
>> As I said, it's not a problem with handling DOS-style paths, but with
>> command-line options being treated as POSIX-style paths.
>
> Sorry if I'm missing some prior discussion,
No, I'm the one who missed some prior discussion ;-)
> but have you tried using a
> double forward slash? My own understanding of this is still quite
> fuzzy but at least in some cases a parameter starting with '//' is
> NOT translated to a DOS name and the extra '/' is removed.
Jonathan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Next Message by Date:
click to view message preview
Running .bat files
Hi all,
Currently, to execute makefiles for Windows toolsets that come with .bat files
for setting environment variables, I'm using the following laborious process:
1. run the .bat file from cmd.exe
2. cd to the MSYS root directory
3. run msys.bat
4. cd to the makefile directory
Can any of this be shortened? In particular, is there a way to run the .bat file
from MSYS (I'm getting the error "fg: no job control") or to run msys.bat from a
directory other than the MSYS root (I'm getting the error "Cannot find the
rxvt.exe or sh.exe binary -- aborting")?
Best Regards,
Jonathan Turkanis
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Previous Message by Thread:
click to view message preview
Re: Re: Description of MSYS in forthcoming C++ Cookbook, by O'Reilly
Jonathan Turkanis wrote:
> As I mentioned in a reply to Greg Chicares, which I just sent, my
> problem is that command-line options using "/" are [interpreted] as
> POSIX-paths. Some Windows tools don't allow command-line options
> beginning with - instead of /.
And for those, you type the command as "foo //option ..."; this is
documented in the README file distributed with MSYS.
HTH.
Regards,
Keith.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Next Message by Thread:
click to view message preview
Linking to wsock32
I have a simple question I hope you do not mind I ask here. I have on
old Makefile which I want to use to compile a program on MS Windows with
MinGW. Makefile:
>>>>>>>>>>>>>>>>>>
CC = gcc
OBJS = gnuclient.o gnudoit.o gnuserv.o gnuslib.o getop.o
ALL = gnuclient gnudoit gnuserv
#INCLUDES = -I/afs/cs/misc/lemacs/build/src/lemacs-19.9/src -I.
CFLAGS = -O -g $(DEFINES) $(INCLUDES)
LDFLAGS = -lwsock32
all: $(ALL)
gnuclient: gnuclient.o gnuslib.o gnuserv.h getopt.o getopt.h
$(CC) $(LDFLAGS) -o gnuclient gnuclient.o gnuslib.o getopt.o
<<<<<<<<<<<<<<<<<<<
The compilation seems to run ok, but linking fails:
gcc -O -g -c -o gnuclient.o gnuclient.c
gcc -O -g -c -o gnuslib.o gnuslib.c
gnuslib.c: In function `GetEmacsPath':
gnuslib.c:442: warning: passing arg 6 of `RegQueryValueExA' from
incompatible pointer type
gcc -O -g -c -o getopt.o getopt.c
gcc -lwsock32 -o gnuclient gnuclient.o gnuslib.o getopt.o
gnuclient.o(.text+0x3f0): In function `main':
C:/Program Files/Emacs/setup/bin/src/GnuServe2a/gnuclient.c:337:
undefined reference to `gethostname
@8'
gnuclient.o(.text+0x6de):C:/Program
Files/Emacs/setup/bin/src/GnuServe2a/gnuclient.c:440: undefined
reference to `WSACleanup@0'
gnuslib.o(.text+0x171): In function `show_wsa_error':
.......................
I have not built libwsock32.a myself, it comes with MinGW. What should I
do to be able to link? I am using MinGW 4.1.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
|
|