poco icon indicating copy to clipboard operation
poco copied to clipboard
verified publisher icon pocoproject

ProGen does not properly generate Target Name

Open aleks-f opened this issue 3 years ago • 5 comments

image

aleks-f avatar Jul 06 '22 09:07 aleks-f

Eg. for debug libraries, it should be Poco$ProjectName)64d

aleks-f avatar Jul 06 '22 09:07 aleks-f

@aleks-f Is this affecting all VS versions or just VS2022?

hmartinez82 avatar Jul 31 '22 21:07 hmartinez82

Regarding the Target Name, I can't reproduce it. Using the devel branch, I built progen with VS2019 and progen'd the Crypto and Net projects just to see if Target Name was being set. And it is. The Test Suite projects are correct to for all archs and configs (Win32 screenshot below): image

hmartinez82 avatar Jul 31 '22 22:07 hmartinez82

I guess I'll have to check why/how I experienced this. I believe it was with VS 2015.

aleks-f avatar Aug 01 '22 06:08 aleks-f

It would be good to have a CI entry where progen regenerates all release libraries projects and builds them. right now we only have cmake-based windows CI.

Although, to be fair, VS projects (and unix makefiles) are a legacy relics which we core devs keep for convenience, cmake is the official build system.

aleks-f avatar Aug 01 '22 10:08 aleks-f

This issue is stale because it has been open for 365 days with no activity.

github-actions[bot] avatar Aug 02 '23 02:08 github-actions[bot]

This issue was closed because it has been inactive for 60 days since being marked as stale.

github-actions[bot] avatar Oct 01 '23 02:10 github-actions[bot]