Jump to content

  • Log In with Google      Sign In   
  • Create Account

#Actualfir

Posted 03 June 2014 - 09:16 AM

 


on the opposite each module includes that summaric folder - there is a little inconvenience becouse i must write something like
 
 
c:\mingw\bin\g++ -O3 -w -c phys_scanline.c -fno-rtti -fno-exceptions -I ..\..\..\
 
 
this "-I ..\..\..\" is needed for reach this main summaric header up the folder tree

 

This is kind of unusual - typically your build system will keep track of the root source directory and all includes are done relative to it, this is best especially if your headers are going to be consumed by others, since they won't be including your headers from their respective directories, so if they all #include other headers relative to their own location in the header tree, well, it isn't going to work. 

 

What do you mean? Can you say how the build systems do that?

(I did not understood)

 

in my system I probably could define some bat variable containing root of my project like c:\code then use this variable instead of  relative "-I ..\..\..\"  (this "-I ..\..\..\" makes problems in refectoring becouse it can be "-I ..\..\..\" but "-I ..\..\" or "-I ..\..\..\..\"  in another bat) but I distaste such hard references yet more than this relative ones  (If i move my root folder the c:\code2 i then woulfd have to change this path - or is there some way of automatic obtaining it in some building scripts so it would be working?)

 

What do you mean that building systems "keep track" on this - what is the way such systems do?

 

(on the rest i will answer a bit later im going to eat something)

 

ps. if we talking about it is there a way of running my compiling bat

like

 

set PATH=c:\mingw\bin;

c:\mingw\bin\g++ -O3 -w -c frame.c -fno-rtti -fno-exceptions -I ..\..\
 
not to wrote with hand name of the module (here "frame.c")
but to make them take the only one .c file avaliable in the folder and insert it automaticaly here? (this way i culd spare a work of handwritting this in each of 400 compiling bats)

#1fir

Posted 03 June 2014 - 09:08 AM

 


on the opposite each module includes that summaric folder - there is a little inconvenience becouse i must write something like
 
 
c:\mingw\bin\g++ -O3 -w -c phys_scanline.c -fno-rtti -fno-exceptions -I ..\..\..\
 
 
this "-I ..\..\..\" is needed for reach this main summaric header up the folder tree

 

This is kind of unusual - typically your build system will keep track of the root source directory and all includes are done relative to it, this is best especially if your headers are going to be consumed by others, since they won't be including your headers from their respective directories, so if they all #include other headers relative to their own location in the header tree, well, it isn't going to work. 

 

What do you mean? Can you say how the build systems do that?

(I did not understood)

 

in my system I probably could define some bat variable containing root of my project like c:\code then use this variable instead of  relative "-I ..\..\..\"  (this "-I ..\..\..\" makes problems in refectoring becouse it can be "-I ..\..\..\" but "-I ..\..\" or "-I ..\..\..\..\"  in another bat) but I distaste such hard references yet more than this relative ones  (If i move my root folder the c:\code2 i then woulfd have to change this path - or is there some way of automatic obtaining it in some building scripts so it would be working?)

 

What do you mean that building systems "keep track" on this - what is the way such systems do?

 

(on the rest i will answer a bit later im going to eat something)


PARTNERS