[nahumb]

Thanks again.

Yes, indeed not recommended (nor fun)…..

Any chance you will provide it in the near future?

Thanks,

Nahum.

[nahumb]

OK Thanks.

Can you please guide me to the .props dirs/files used by VGDB to build the remote/cross Qt/MSBuild versions?

Thanks,

Nahum.

[nahumb]

Thank you for the reply.

Sorry, but I don’t understand what do you mean by: “Finally apply the same custom rules to the newly created MSBuild project”

Can you please provide me with more detailed instructions/tutorial/demo?

Thanks,

Nahum.

• This reply was modified 6 years ago by nahumb.

[nahumb]

Please also note the following build messages

2>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(38,3): warning MSB4011: “C:\Users\Nahum\AppData\Local\VisualGDB\FindComponents.props” cannot be imported again. It was already imported at “E:\Nahum\Workspace\RaspberryPi3\Projects\VS\AdjHeartRapiSynth1.0\AdjHeartRapiSynth1.0\AdjHeartRapiSynth1.0.vcxproj (48,5)”. This is most likely a build authoring error. This subsequent import will be ignored.
2>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(73,2): warning : Missing toolchain profile for 192.168.3.2, ID=’com.sysprogs.toolchain.default-gcc’, version=”. IntelliSense may produce incorrect results.

Thanks,

Nahum.

[nahumb]

Once again thanks for the prompt and helpful reply. The MSBuild option, as suggested works fine.
I would like now to use the cross compilation option and let my quad-core i7 do the hard work and not the Raspberry Pi using the build over the network option, as demonstrated in the tutorials presented so far.
What should be changed in the processes of converting the Qt project (other than the commands paths) into MSBuild and creating the library?

My next issue is, is there a way to set IntelliSence to recognize the library context (other than manually adding the .h files)?

Thanks,

Nahum Budin.

[nahumb]

So I have walked through the .props file (for the 1st approach) again, only to find out 2 fault spaces on the long lines :-(.
Once removed, solution is now loaded and build successfully using MS build.
However, every time I load the solution I get the following error message: “The selected toolchain is missing the MSBuild rule files. Do you want to regenerate them?”
I select “Yes”, I get a dialog running Preparing Toolchain for MSBuils…. , but next time I load the solution I still get the error message.

And please also do not forget my question regarding linking a static library to another static library.

Thanks,

Nahum Budin.

[nahumb]

Hi,

Thanks for the prompt reply.

I was trying to implement the 1st solution but after adding the Target Section XML lines from the tutorial to the .props file (the 2 GenericGNUtool sections),
the project loading by VS failed.
(I could not use the full file in the example, as it is using Qt5 while I’m using Qt4 (and its a long story why I haven’t been able switching to Qt5).

So I tried the second approach.
It works, but raised a new issue.
In my case, I would like to build a static library that in addition to my code, links to other static libraries (e.g. Bluetooth), so it will be easier
to use my (integrated) library that wraps the other libraries services with a higher level API.

Is there a way to do it (I know that VS has the lib tool)?

Thanks,

Nahum Budin.

[nahumb]

And one more piece of information, if applicable, Linux machine = Raspberry Pi.

Thanks,

Nahum Budin.

[Author]

Posts