[jmkresse]

Ah! Thanks!

[jmkresse]

Thanks! That helped a lot!

Now, there is still the issue that if I specify an optimization level of -Ofast, it is ignored. (And I am using VisualGDB 5.2r9.)

Thanks!

[jmkresse]

And I tried entering -Ofast, but it ignores it.

Attachments:

You must be logged in to view attached files.

[jmkresse]

I enabled global verbose mode, but it still didn’t show me what the compiler command was when it executed it.

Attachments:

You must be logged in to view attached files.

[jmkresse]

Thanks!

What is the best/recommended way to specify the -Ofast compiler option (instead of -O3, for example). It’s not one of the listed optimization options.

(I think I found a workaround, but don’t know if it’s the best/recommended way.)

Thanks!

[jmkresse]

Thanks! It looks like I got things working.

[One note: MSBuild puts the object files, the executable, and the map file in different places than Gmake, so I also had to adjust things so they would end up in the same directories that Gmake used (we have scripts which rely on the executable and map file to be in a certain directory).]

[jmkresse]

Thanks for this information.

I am still having problems, though, with getting this to work. It looks like I am possibly having problems with the syntax for the directory separator. For the Map file name, I have tried Debug/xxxxx.map, Debug\xxxxx.map, Debug\/xxxxx.map, and other permuations without success. What is the correct syntax for this?

(And I am having a similar problem with one of my Preprocessor Definitions. When I use Gmake, I used -DTH_FILE_DIR_PATH=\”../IOFiles/\”, and again, with MSBuild, I have tried various permutations of “, /, and \ without success. What is the appropriate syntax for MSBuild?)

Thanks!

[jmkresse]

The problem has disappeared. I had moved some of the source files around, and did a complete rebuild, so that may be why it disappeared. If it happens again, I will try your suggestions.

Thanks!

[jmkresse]

Thanks! So if I have one project dependent on another, if I build the “upper” project, it will automatically build the “lower” project, if it is out of date?

And we need to stick to using GNU Make because we may eventually also do these builds on a different platform which only has GNU Make available.

[jmkresse]

I was afraid of that; but, again, that’s not possible for me.

As a workaround, is it possible to have one project dependent on another one?

 

[jmkresse]

Sorry, for compatibility reasons, I have to use GNU Make, not MSBuild.

[jmkresse]

I would suggest trying

printf(“%f\r\n”, 1.5);

to see if that works for you.

[jmkresse]

Thanks for this information!

[jmkresse]

I reverted the directory to an earlier, known good, version, and the issue has gone away. If it reappears, I will try these steps.

Again, I’m using GNU make, not NMake.

Also, can you explain what you mean when you say:

When you hold Shift, does the VisualGDB Project Properties window show the correct settings?

Thanks!

[jmkresse]

Now it doesn’t even show the VisualGDB settings in the Solution Explorer, or show “VisualGDB properties” under Project.

Do I need to redo the entire project?

[Author]

Posts