Bug 204824

Summary: devel/poco and devel/poco-devel packages doesn't install PocoConfig.cmake
Product: Ports & Packages Reporter: Heather <heather>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me CC: henry.hu.sh, joe, rakuco
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Heather 2015-11-26 08:23:17 UTC 
I need PocoConfig.cmake to include it in other cmake projects (alike opencv library installs cmake config and I can simply import it into my cmake project)

I was trying to build poco-devel from ports and including /usr/ports/devel/poco-devel/work/poco-poco-1.6.0-release/cmake/PocoConfig.cmake

But this either didn't helped because as is it can't find Poco headers (not sure if this issue also partly depends on Poco itself)

But here is related issue I opened on github: https://github.com/pocoproject/poco/issues/1045
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2015-11-26 16:52:39 UTC 
Fix Summary and notify both maintainers.
Comment 2 Raphael Kubo da Costa freebsd_committer freebsd_triage 2016-01-06 16:09:32 UTC 
The port's build system is weird: the CMake files are installed only if CMake is used to build Poco.

Option 1 is to switch to CMake (and fetch the -all version of the tarball), option 2 is to manually install those files while still using Poco's homebrewn build system.
Comment 3 Heather 2016-01-14 08:02:23 UTC 
Hello, I will be happy already at least having dirty workaround on this to run my build system for my software with this

Thank you
Comment 4 Raphael Kubo da Costa freebsd_committer freebsd_triage 2016-02-25 12:18:51 UTC 
Drop maintainer-feedback request for wes@, he's been inactive for years.
Comment 5 Raphael Kubo da Costa freebsd_committer freebsd_triage 2016-02-25 12:26:18 UTC 
I was taking a look at this, and installing the Config files without CMake is not just a matter of doing that manually in the port's Makefile: some submodules also have their own Config file, and those need a corresponding "Poco<module>Targets.cmake" file that's generated by CMake itself.

It's probably a better idea to just switch the build system to CMake. The port currently has no maintainer, so anyone interested in this can adopt the port or just send a patch to implement this.
Comment 6 commit-hook freebsd_committer freebsd_triage 2016-08-19 03:53:32 UTC 
A commit references this bug:

Author: marino
Date: Fri Aug 19 03:52:36 UTC 2016
New revision: 420445
URL: https://svnweb.freebsd.org/changeset/ports/420445

Log:
  devel/poco-devel: Older than stable port, deprecate for removal

  The devel version of poco is signficantly behind the stable devel/poco
  which is regularly updated.  There's no apparent benefit to having two
  ports in this case.  I'll mention to the maintainer that devel/poco is
  currently unmaintained in case he wishes to take that over even though
  ports fury has been handling that for a while.

  PR:	204824

Changes:
  head/devel/poco-devel/Makefile
Comment 7 John Marino freebsd_committer freebsd_triage 2016-08-19 03:55:38 UTC 
Joe,
Unless you can come up with a compelling case to keep devel/poco-devel (which would include updating the port), it's going to be removed in a month or so.

If you still want a maintainer role wrt to poco, the stable devel/poco port is currently unmaintained, so you can take it over.  You probably will want to address this PR in that case though.
Comment 8 joe 2016-08-27 15:37:53 UTC 
Sorry for the delay. At this time, I am not interested in being the maintainer for devel/poco.
Comment 9 Henry Hu 2017-03-14 01:52:49 UTC 
It seems like that devel/poco now installs a bunch of cmake files including /usr/local/lib/cmake/Poco/PocoConfig.cmake. Should this PR be closed?
Comment 10 Raphael Kubo da Costa freebsd_committer freebsd_triage 2017-03-14 10:03:40 UTC 
I think so; ports r411170 (which updated devel/poco to 1.7.0) seems to have fixed this. Thanks for pointing this out.