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
Fix Summary and notify both maintainers.
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.
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
Drop maintainer-feedback request for wes@, he's been inactive for years.
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.
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
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.
Sorry for the delay. At this time, I am not interested in being the maintainer for devel/poco.
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?
I think so; ports r411170 (which updated devel/poco to 1.7.0) seems to have fixed this. Thanks for pointing this out.