Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Please add static libraries for OSX to the repository #46

Closed
mike-lischke opened this issue Jul 19, 2015 · 9 comments
Closed

Please add static libraries for OSX to the repository #46

mike-lischke opened this issue Jul 19, 2015 · 9 comments

Comments

@mike-lischke
Copy link

In order to build the gui on OSX I'd need the static libs for it. In the package included seem only Windows static libs. Can you please add those for OSX too? Thank you.

@nmav
Copy link
Contributor

nmav commented Jul 20, 2015

Currently the only way to build on OSX is via MacPorts. That is, until there is a maintainer for an OSX package.

@mike-lischke
Copy link
Author

What do you mean by "until there is a maintainer"? Since openconnect-gui is in Ports there must be a maintainer already. Someone has compiled it for Ports and I'd expect it's the one that maintains this repo (would only be natural, no?).

@nmav
Copy link
Contributor

nmav commented Jul 20, 2015

There is a MacPorts maintainer but that is irrelevant to your question. Macports requires no binaries to be shipped by the project. If we have a maintainer for an OSX binary package it would make sense to ship binary libraries. Until that time I don't think I can help you (I don't even have OSX).

@mike-lischke
Copy link
Author

I see. Too bad then. I'd write a better (native) GUI client for openconnect if I'd had the libs. But without them a good chance will be lost.

@nmav
Copy link
Contributor

nmav commented Jul 20, 2015

Why don't you use the libs compiled by the macports package?

@mike-lischke
Copy link
Author

Unfortunately, there are no libs. It's just a single binary (static libs, remember?).

@nmav
Copy link
Contributor

nmav commented Jul 20, 2015

But if you were able to link with static libs, these should be available somewhere in your system.

@mike-lischke
Copy link
Author

I can't link, since I don't have the static libs. This enhancement request is exactly about this.

@nmav
Copy link
Contributor

nmav commented Jul 20, 2015

If I understand correctly how macports works, it downloads the sources, compiles, links and gives you the executable. In that process it downloads the libraries you wanted, and links with them (statically). So if you build the macports package you already have the openconnect library somewhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants