User forums > Nightly builds
The 21 January 2007 build is out.
killerbot:
looking at the code, it doesn't make sense, a compiler is valid if it's C compiler program can be found [m_Programs.C] [note : C++ compiler can always do C too]., either in the MasterPath or in the extra Paths, the fact that "additional paths " is empty should not make it invalid, and so says the code. :shock:
Are you really sure you didn't have another problem ??
What did you specify as MasterPath (could be maybe in your masterpath you already specified the bin subdir, you shoulnd't , CB itself will append the bin subdir).
And for additional paths it doesn' t add anything, so when this might be set to the MasterPath (ending with the bin) dir, this could explain that in your case with your change it now works. But as far as I can see, it is correct, so no need for code changes.
killua:
--- Quote from: killerbot on January 22, 2007, 05:35:37 pm ---looking at the code, it doesn't make sense, a compiler is valid if it's C compiler program can be found [m_Programs.C] [note : C++ compiler can always do C too]., either in the MasterPath or in the extra Paths, the fact that "additional paths " is empty should not make it invalid, and so says the code. :shock:
Are you really sure you didn't have another problem ??
What did you specify as MasterPath (could be maybe in your masterpath you already specified the bin subdir, you shoulnd't , CB itself will append the bin subdir).
And for additional paths it doesn' t add anything, so when this might be set to the MasterPath (ending with the bin) dir, this could explain that in your case with your change it now works. But as far as I can see, it is correct, so no need for code changes.
--- End quote ---
My master path was pointing to c:\<install path>\bin . I was unable to compile anything due to this. I added the Additional Path and pointed it to the same directory as the master path.
After reading your above post, I removed the \bin on the master path, removed the additional path, and it works as it would normally.
I had never messed with that option before (the master path) until today. /boggle
killerbot:
probably you set it like this at the time you added the compiler.
By the way, which compiler was it ??
killerbot:
anyhow, tomorrow I will add an extra search criteria, where it also looks in the MasterPath without appending the bin dir, then it doesn't matter if the bin is already in your MasterPath, but it is adviced not to include the bin dir in the value of MasterPath, as does the NOTE say in the Programs tab [personal note : our code was not consistent with the note, since when looking for the exe to actually build (!= check if Valid) we apparently look in the MasterPath itself also without appending the bin dir, where as the note says : either in the bin subdir or the additional paths]
I would suggest we don't play strict as the note says and we ???????adjust the note???????, why not strict : suppose there's a compiler package which does not have a bin subdir ....
killua:
--- Quote from: killerbot on January 22, 2007, 06:17:01 pm ---probably you set it like this at the time you added the compiler.
By the way, which compiler was it ??
--- End quote ---
My install was from the RC2 install with minGW. I haven't bothered to change it since then.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version