Overlay package gets installed in wrong location #107

Open
gegenschall opened this Issue May 15, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@gegenschall

After updating Visual Studio 2013 to Update 4 several problems started appearing with one specific package (OpenCV 2.4.10) that uses Overlays:

For some project I have this line in my packages.config in the project root:

<package id="OpenCV" version="2.4.10" targetFramework="Native" />

Doing nuget.exe restore correctly installs the package to $(SolutionDir)packages\. Upon building of the project it seems that nuget tries to install an overlay packge which succeeds but it gets installed in the wrong location thus .lib and .dll files cannot be found when linking. The error message is:

warning : Overlay Package 'OpenCV.overlay-x64_v120_Debug v2.4.10' installed correctly, but the nupkg file 'C:\project\packages\OpenCV.2.4.10\OpenCV.overlay-x64_v120_Debug.2.4.10' is not in the expected location.

It really isn't there, its at the top-level package source location or sometimes at the project root.
How do I fix this?

@gegenschall gegenschall changed the title from Problem with overlay package to Overlay package gets installed in wrong location May 15, 2015

@Thieum

This comment has been minimized.

Show comment
Hide comment
@Thieum

Thieum Aug 20, 2015

👍 same issue here.

Thieum commented Aug 20, 2015

👍 same issue here.

@Thieum

This comment has been minimized.

Show comment
Hide comment
@Thieum

Thieum Aug 20, 2015

A workaround is to prevent the creation of overlays altogether as explained in #54 .

Thieum commented Aug 20, 2015

A workaround is to prevent the creation of overlays altogether as explained in #54 .

@zer0n

This comment has been minimized.

Show comment
Hide comment
@zer0n

zer0n Jul 23, 2016

I run into the same issue. @gegenschall, have you found the cause and solution for this issue?

zer0n commented Jul 23, 2016

I run into the same issue. @gegenschall, have you found the cause and solution for this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment