how to generate the intermediate files (i.e.,*.s, *.i ) in a different directory ?

rpittala · 05-12-2017, 11:42 AM

my question is on how to force generate the default generated files location to a certain location ?

Lets say I have the below rule in my makefile(Clearmake):

Quote:

.c.o: $(SOURCE_TOOLS)
$(CC) \
$(STANDARD_OPTIONS) \
$(VARIABLE_OPTIONS) \
$(CODE_LOCATION_OPTIONS) \
$(COMPILE_SWITCHES) \
$(INCLUDE_PATH) \
-c -dg $< -o $@ \
2>&1

I run the makefile at /home/user/ . So, the ".o" file generate at the corresponding location of ".c" files, this is as expected.

When I pass the "-dg" highlighted in bold in the above code, it generates "*.c.100.dg" file at the current working directory. So, I need this intermediate file in /home/user/debug_files/. I can not change the path of running the makefile.

pan64 · 05-12-2017, 11:52 AM

this is not related to clearcase, but the compiler you use. if there was no other way you can add a line:
<tab>mv *dg /home/user/debug_files/
or similar

rpittala · 05-12-2017, 12:13 PM

Hi Pan64,

That`s a quick thought. I have tried it as

Quote:

.c.o: $(SOURCE_TOOLS)
$(CC) \
$(STANDARD_OPTIONS) \
$(VARIABLE_OPTIONS) \
$(CODE_LOCATION_OPTIONS) \
$(COMPILE_SWITCHES) \
$(INCLUDE_PATH) \
-c -dg $< -o $@ \
2>&1
$(MV) -f *.c.100.dg $(DEBUG_PATH)/

and it fails saying mv: cannot stat `*.c.100.dg': No such file or directory

am I placing the right "mv" command at right place ? is it possible (or) do we have a rule to move/generate the files as and when the *.c.100.dg files generated ?

sundialsvcs · 05-12-2017, 05:00 PM

Naah, that seems to me to be a red-herring dead end: you don't want to move the files. You just gotta see if your compiler has a command-line option that will specify where its output files should be placed.

rpittala · 05-12-2017, 06:16 PM

Yes, I referred the user manual for the same and I did not find any of such option and the compiler is HIGHTEC GCC

pan64 · 05-12-2017, 11:58 PM

I do not really know that compiler, so I don't know where should you put that line. You posted one line of a makefile, that will not help a lot....
Also I do not know if moving those files is a good idea or not. But if those files were generated during execution of .c.o rules (together with .o files) the mv command should be ok, although I would use $<.100.dg probably, and also insert a - before the command.

rpittala · 05-13-2017, 03:06 AM

Great !

It’s possible that I’m going crazy because that time it did fail and now, it is moving the files. But, still some error messages as:

mv: cannot stat `os_msc_init.c.100.dg': No such file or directory

Any ways it is moving the files to the desired location. Tried suppressing the error messages as:

Tried with $(MV) -f *.c.100.dg $(DEBUG_PATH) 2>/dev/null
failed with error code 1

Looks like delaying the MV command would resolve the issue. How can I check the the file existence:

Tried with this:

Quote:

if [ -e "*.c.100.dg" ]; then \
$(MV) -f *.c.100.dg $(DEBUG_PATH) 2>/dev/null; \
fi

Now again,it is not moving the files.

NevemTeve · 05-13-2017, 03:56 AM

First, use command ls -ltr to find out the names of generated files, then edit you Makefile... Sg like this

Code:

.c.o: $(SOURCE_TOOLS)
        $(CC) \
        $(STANDARD_OPTIONS) \
        $(VARIABLE_OPTIONS) \
        $(CODE_LOCATION_OPTIONS) \
        $(COMPILE_SWITCHES) \
        $(INCLUDE_PATH) \
        -c -dg $< -o $@ \
        2>&1
        -$(MV) -f *.dg $(DEBUG_PATH)/

rpittala · 05-13-2017, 05:24 AM

I am not interested in the names. But, with their extension(*.dg).

Why do we need file names ?

Quote:

if [ -e "*.c.100.dg" ]; then \
$(MV) -f *.c.100.dg $(DEBUG_PATH) 2>/dev/null; \
fi

If you can suggest me on how to make the above condition successful that would be very helpful

pan64 · 05-13-2017, 05:27 AM

without knowing the compiler and knowing what's really happening .....
You ought to be strict, so move only the "current" .dg file(s), not the one created by another target (otherwise you may have very strange error messages)

rpittala · 05-13-2017, 05:53 AM

Mine is a HITECH compiler which runs on Linux server and still using the Clearmake Makefile

I think there won`t be much difference in from the GNU compiler.

NevemTeve · 05-13-2017, 06:32 AM

> I am not interested in the names. But, with their extension(*.dg).

Trouble is, you know neither. Or if you know, you cannot properly tell. Also you fail to see difference between [quote] and [code] Nonetheless, here is your code:

Code:

.c.o: $(SOURCE_TOOLS)
        $(CC) \
        $(STANDARD_OPTIONS) \
        $(VARIABLE_OPTIONS) \
        $(CODE_LOCATION_OPTIONS) \
        $(COMPILE_SWITCHES) \
        $(INCLUDE_PATH) \
        -c -dg $< -o $@ \
        2>&1
        -$(MV) -f *.dg $(DEBUG_PATH)/ 2>/dev/null

rpittala · 05-13-2017, 10:15 AM

Okay fine.

I tried

Code:

$(basename $(@F))

Code:

if [ -e "*.c.100.dg" ]; then \
$(MV) -f *.c.100.dg $(DEBUG_PATH) 2>/dev/null; \
fi

to get the file name and did not work. So, I just continued with the above IF condition.

Thanks for pointing out the difference between [QUOTE] and [CODE].

Quote:

Trouble is, you know neither. Or if you know, you cannot properly tell.

What else you want to know other than my above reply's

NevemTeve · 05-13-2017, 10:53 AM

Please let's start from the very beginning: What is in your Makefile? What do you expect to happen? What happens instead of that? Is there an error message?

pan64 · 05-13-2017, 10:57 AM

Quote:

if [ -e "*.c.100.dg" ]; then

this is definitely wrong, there is no file named *.c.100.dg. Would be nice to give us some real file names, examples about what's happened.