Trouble creating vcpkg port about cbc

[svigerske]

Running the usual configure/make/make-install is preferred, in my opinion. What I meant was that it is best to avoid recreating configure, etc, by running autoreconf. Just use the configure that is distributed.

[svigerske]

Don't attempt to autoreconf. microsoft/vcpkg#31607 (comment) is correct.

For current Cbc releases, you'll have to live with the configure script that is generated by a very old autotools.
Branch master has been updated for use with very recent autotools years ago, but no release from that branch is in sight.

[jpfeuffer]

So if I chose to build from a specific point on master, it should work?
Which version of buildtools do I need to use then? Latest (0.8) or also master?

[jpfeuffer]

I am just wondering how the rest of the coinor packages work flawlessly on vcpkg.
I noticed that they are not using release versions but dates, so they might be builds from master.

[svigerske]

You can try with the current master and try to avoid running autotools (autoreconf, etc). But if you have to, then use current master of BuildTools. That applies additional patches for builds with MS/Intel compilers on Windows.

I have no experience with vcpkg.

[jpfeuffer]

Ok thank you very much! Last (newbie) question: what is the alternative to autotools for cbc? What should I run instead?

[jpfeuffer]

Hi!
I now managed to build it on all platforms but Windows which seems to have problems with pkgconfig and its paths.
See microsoft/vcpkg#31607 (comment)

Do you have any idea how to solve that?