topic Re: Making separate deployment in Operating System - HP-UX

Making separate deployment

Vibhor Kumar Agarwal — Wed, 06 Apr 2005 00:53:58 GMT

Hello,

I have started using HP-UX just a week ago.
Prior i was working on Solaris.

To my extreme discomfort all my makefiles have stopped working here.
In solaris to prepare separate deployment I used:

-o $@ tag in build command to produce the output files.

I used to prefix path in .o like
/disk1/Deployement/A.o
/disk1/Deployement/B.o
etc,

Now my rule is
/disk1/Deployment/%.o:%.cpp
$(BUILD) $<
where $(BUILD) contains all compiler specific tags.

This used to work in solaris but here it gives error "Don't know how to make A.o" and subsequently all .o

Please help
Thanks in Advance

Re: Making separate deployment

Ermin Borovac — Wed, 06 Apr 2005 01:18:31 GMT

Please try

.cpp.o:
$(BUILD) $<

Re: Making separate deployment

Vibhor Kumar Agarwal — Wed, 06 Apr 2005 02:51:24 GMT

For this to work i have to remove the path prefix from the .o, otherwise it gives the same error. ( Don't know how to make )

On removing the prefix it creates the .o's in the same directory.

Re: Making separate deployment

Ermin Borovac — Wed, 06 Apr 2005 21:03:45 GMT

Would the following makefile accomplish what you are after? It assumes sources and Makefile are in the current directory and objects go to /disk1/Deployment.

VPATH=/disk1/Deployment
OBJ=$(SRC:.c=.o)
all:
@$(MAKE) TARGET src="`echo *.c`"
TARGET: $(OBJ)
.c.o:
$(BUILD) $< -o $(VPATH)/$@

Re: Making separate deployment

Vibhor Kumar Agarwal — Thu, 07 Apr 2005 01:06:22 GMT

Just a small confusion:

What does this line do
@$(MAKE) TARGET src="`echo *.c`"

As far as i have tried it makes the .o in the destination directory which i am able to achieve.
But during linking it can't find those .o's as its searching for them in the current directory.
How do i accomplish only this linking part.

Re: Making separate deployment

Ermin Borovac — Thu, 07 Apr 2005 02:47:07 GMT

For linking part you can simply cd into /disk1/Deployment directory and run ld from there.

Line that does `echo *.c` is to get around the pattern matching problem. It defines variable SRC which holds a list of all source files. Variable OBJ holds list of all object files, obtained from SRC where .c is substituted with .o suffix.

Here is a full example

VPATH=/disk1/Deployment
OBJ=$(SRC:.c=.o)
all:
@$(MAKE) $(VPATH)/a.out src="`echo *.c`"
$(VPATH)/a.out: $(OBJ)
cd $(VPATH); ld -o a.out /usr/ccs/lib/crt0.o $(OBJ) -lc
.c.o:
cc -c $< -o $(VPATH)/$@

Re: Making separate deployment

Vibhor Kumar Agarwal — Thu, 07 Apr 2005 06:02:52 GMT

Bingo,

Thanks.

Gotcha.

All what i had to do was cd into the directory and then do linking.

One small confusion: my script was not working because i was using
%.o:%.cxx instead of .cxx.o

This % thing doesn't seem to work on HP-UX as its giving me an error
CC -0 -c ../source/file
Make: Cannot load CC. Stop.

But as soon as i replace
%.o:%.cxx with .cxx.o
everything works.

Since make isn't specific to any flavour of Unix then why is this thing happening?

Any comments.