Alternatively, I've made a small change to my qmacros.mk
(c:/QNX632/target/qnx6/usr/include/mk/qmacros.mk or whatever) to pass just
the file name and not the entire path to usemsg and this seems to avoid the
problem quite nicely.

Just change:

define ADD_USAGE
	$(if $(UMPREF),$(UMPREF) $(addprefix -i,$(tag_list))
$(ADD_VERSIONING) $@ $(USEFILE) $(UMPOST))
endef

to

define ADD_USAGE
	$(if $(UMPREF),$(UMPREF) $(addprefix -i,$(tag_list))
$(ADD_VERSIONING) $(notdir $@) $(USEFILE) $(UMPOST))
Endef


Roger


-----Original Message-----
From: Colin Burgess [mailto:cburgess@qnx.com] 
Sent: January 14, 2008 11:59 AM
To: general-toolchain
Subject: Re: backslashes in binary name when invoking pidin

It's inserted by ldrel (which is invoked by usemsg).  This is fixed in the
head branch kernel.
You can remove it by stripping your binary (but that will also remove the
use message).  To my knowledge if you use the objcopy argument to use then
it will not add it (since it is not using ldrel)

Colin

Freddy Martens wrote: 

Hi all, 

I am noticing backslashes in my binaryname when invoking pidin. Example:
c:\workspace\my_project\o_g\my_bin 

This prevents 'slay' to kill the process. Can you tell me what I am missing?


TIA,
Freddy 


_______________________________________________ 
General 
http://community.qnx.com/sf/go/post4271
<http://community.qnx.com/sf/go/post4271>;  


-- 

cburgess@qnx.com <mailto:cburgess@qnx.com>; 

_______________________________________________
General
http://community.qnx.com/sf/go/post4272