Paket and C++ projects?

[konste]

My colleague reported that Paket does not work right for C++ projects, while NuGet does.
What is the design decision here - is it even supposed to support C++ projects or not?
If it supposed to support C++, then I gather more details about the problem from my colleague.
If it is not supposed to support C++, then can we have Paket and NuGet used in the same solution?

Thank you!
Konstantin

[forki]

yes please give details. Maybe it's just fixing https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/ProjectFile.fs#L229 and https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/ProjectFile.fs#L108

[forki]

I will try it out

[forki]

what is the correct project file ending?

[forki]

Ok. let's make this a thing. paket 2.50.0 comes with experimental support for vcxproj. Please let me know how badly it breaks you.

[konste]

Looks encouraging... But we are brave! My colleague Tommy, who mostly cares about C++ will be looking at it shortly. Thanks for the swift response!

[forki]

yeah I added a small integration test with a "file new C++ project". It seems to reference it correctly, but I assume this is only the tip of the iceberg.

[tommysu]

Thanks, I plan on giving a go today. A quick question will be what do you recommend we put for the "framework" or should I just leave that out?

[forki]

in the dependencies file?

Good question. I guess start by leaving it out.

[forki]

to clarify: I want to make this useful for C++, but since I don't use C++ myself it will likely involve some ping pong during the initial dev/testing phase.

[tommysu]

Yea, in the dependencies file. I'm going to try it empty. In nuget we would do something like this: . I'm giving 2.50 a try and will let you know soon the result.

[forki]

better remove the line completey (at least for now) we can add it back later when we know the correct framework monikers.

[tommysu]

This was able to include the library files correctly. However, one thing that it was missing was the target files.

An example is:

 <ImportGroup Label="ExtensionTargets">
    <Import Project="..\packages\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn.2.7.0\build\native\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn.targets" Condition="Exists('..\packages\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn.2.7.0\build\native\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn.targets')" />

When following the nuget instructions for this package:

https://github.com/Microsoft/cpprestsdk/wiki/Getting-Started-Tutorial

[forki]

ok will look at this tommorow.

[forki]

@tommysu can you please send me the project that you get after "getting started" using Nuget? sforkmann at gmail

[tommysu]

Sent.

[forki]

I'm pushing a new version but I'm not sure if the "when conditions" are generated properly. So I assume we need to iterate on that. But it is progress ;-)

[forki]

Ok release failed. I broke another integration test. Good thing that we have these in place. Will look into this tomorrow.

[forki]

Ok the version is released

[tommysu]

It appears that the project file will get corrupted it. It generates a When condition with uneven number of ' marks. And Visual Studio will complain of An unexecpted token "=="

 <Choose>
    <When Condition="$(Platform)'=='Debug|Win32'">

[forki]

ah. my copy paste bug. fixing it now.

[forki]

fixed that

[tommysu]

Sorry for going back and forth. But it looks like the target file path is incorrect.

<Import Project="..\packages\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn\build\$(__paket__cpprestsdk_v120_winapp_msvcstl_dyn_rt-dyn_targets).targets" Condition="Exists('..\packages\cpprestsdk.v120.winapp.msvcstl.dyn.rt-dyn\build\$(__paket__cpprestsdk_v120_winapp_msvcstl_dyn_rt-dyn_targets).targets')" Label="Paket" />

It should be something like \build\native$(...).targets

[forki]

Ah I see. Yes this is completely different to the other target framework
stuff.
On Feb 11, 2016 10:44 PM, "tommysu" [email protected] wrote:

Sorry for going back and forth. But it looks like the target file path is
incorrect.

It should be something like \build\native$(...).targets

—
Reply to this email directly or view it on GitHub
#1467 (comment).

[forki]

Ok another fix deployed. Please run "paket clear-cache" before you try again.

[tommysu]

Awesome, that works! I'll let you know if I run into any more issues.

[forki]

Wow. Cool.
On Feb 13, 2016 8:35 PM, "tommysu" [email protected] wrote:

Awesome, that works! I'll let you know if I run into any more issues.

—
Reply to this email directly or view it on GitHub
#1467 (comment).

[forki]

Closing this one.

Please open new issues for the new issues you find.