[victor_s]

Thank you very much for this detailed explanation. Moving import right after Microsoft.Cpp.Default.props made everything work as expected.

[victor_s]

Thank you.

I found that VisualGDB specific properties do change from the property sheet. It just can’t be seen and controlled from the project property page, like other properties, so it is sort of hidden properties. No matter what written in the project property page – settings always taken from property sheet.

In some situations it can be misleading, like you define something in the property page and it doesn’t work, because property sheet redefined it.

[victor_s]

Thank you, it works for common Visual Studio properties, like <Outdir> or <ClCompile>

But I didn’t succeed to define VisualGDB specific properties like <GNUConfigurationType>, <GNUToolchainPrefix>, <GNUCompilerType>.  Can it be done?

[victor_s]

Hello. Do you plan to integrate it to the main version (release) some time?

[victor_s]

When I turn on verbose mode for a linker – I see “GNU ld” working.

[victor_s]

Hello.

Another issue here – how can I make sure that VisualGDB uses xild for linking and not ld. I suspect that it doesn’t.

[victor_s]

It works nice with this build. Thank you very much.

[victor_s]

Compiling works, but it fails at the link stage. It still looks for g++ for linking.

[victor_s]

Great. Thank you.

I see in verbose mode that intel compiler runs. I need to make additional testings yet.

[victor_s]

Thank you for the help. I want to try a new build. Working with MSBuild is better for me.

Did you mean GCCFlags.xml? However I think icc flags are mostly compatible with gcc.

[Author]

Posts