Enable disabled techs

[Mark_T]

Sadly no. It seems rather random. Sometimes it starts compiling in the middle of the list of files, sometimes it only takes the edited files and sometimes it starts from scratch (often if I haven't edited the code for a while; as if there's some kind of time-out).

I got the function working though.

 

[EmperorFool]

Most good tools with compilers will build automatically in the background after a change, starting over if you make another change in mid-compile. It should never block you from continuing to make more changers; that's just lame.

 

[xienwolf]

I am guessing that he means that when he is done writing what he wants to write for this go-through, it is compiling every file, but other times it is only compiling 2 or 3 files.

The catch is the *.h files. Any change in a .h will require that every file which includes that .h (and I think all files which include THOSE files too) needs to recompile. Essentially this means any change in a Cv___.h requires a complete rebuild, but changes in Cy___.h require only all of the Cy___ files and a handful of other files to also rebuild.

It is because of this that I generally advise people to plan your program in advance, think of all functions & Variables that you are going to need and declare them all, generate the bare bones of each function, but don't tie it into the code yet. Compile your "long run" and check that there are no issues in game (at this point everything should work exactly as it did before your code writing). Once you verify that, THEN you go back into the code and start making it do something.

I personally prefer that while I am making the Bare Bones functionality I also include the text displays so that I can have new fields I created be used somewhere to ensure that the text display comes out properly, even if it doesn't actually do anything yet.

 

[EmperorFool]

. . . it is compiling every file, but other times it is only compiling 2 or 3 files.

Oh ok, that makes more sense. 15 minutes to do a full compile? No, I don't miss C++ that much.

and I think all files which include THOSE files too

That's correct; changing a transitive include (A includes B which includes C) will cause recompilation. You should be able to compile a single .cpp file. While you're adding your functions to X and X's header file, you can test that it compiles before compiling everything that includes X.h.

 

[Mark_T]

Thanks guys. You've been a great help. It's much appreciated.