You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So as the title says I have a project where a lib path doesen't get expanded correctly. Weird thing is other paths. for example includedirs, do get expanded correctly. This is my premake file:
Because of some reason when running the vs2022 action I get this library path generated:
Instead I expect a path more like "C:...\Octopus-Dev\Octopus\vendor\Assimp\assimp-vc143-mtd.lib", Octopus beeing the projects name. Does anyone know why this occurs?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So as the title says I have a project where a lib path doesen't get expanded correctly. Weird thing is other paths. for example includedirs, do get expanded correctly. This is my premake file:
and this is the Dependencies.lua file:
Because of some reason when running the vs2022 action I get this library path generated:
Instead I expect a path more like "C:...\Octopus-Dev\Octopus\vendor\Assimp\assimp-vc143-mtd.lib", Octopus beeing the projects name. Does anyone know why this occurs?
Beta Was this translation helpful? Give feedback.
All reactions