Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OpenLDAP MSYS2 builder #25

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

cmb69
Copy link
Contributor

@cmb69 cmb69 commented Nov 6, 2024

This does a full client build of OpenLDAP, using upstream's autotools based build chain on MSYS2, but using MSVC build tools. This requires wrappers for the MSVC build tools; ar-lib and compile are taken unmodified from automake; windres is a minimalist self-made wrapper.

We also need POSIX regex for the client tools (such as ldapsearch); we use rxspencer[1], which we build on the fly and link in statically.

Using upstream's autotools based toolchain has the obvious drawback that building now requires MSYS2 instead of "native" Windows tools only. On the other hand, instead of needing hand-made configuration and Visual Studio solutions, what is volatile regarding updates of the library, we only need a manageable patch set. Plus, we get the client tools basically for free. If we want to distribute them is another question.

[1] https://github.com/garyhouston/rxspencer

This does a full client build of OpenLDAP, using upstream's autotools
based build chain on MSYS2, but using MSVC build tools.  This requires
wrappers for the MSVC build tools; ar-lib and compile are taken
unmodified from automake; windres is a minimalist self-made wrapper.

We also need POSIX regex for the client tools (such as ldapsearch); we
use rxspencer[1], which we build on the fly and link in statically.

Using upstream's autotools based toolchain has the obvious drawback
that building now requires MSYS2 instead of "native" Windows tools
only.  On the other hand, instead of needing hand-made configuration
and Visual Studio solutions, what is volatile regarding updates of the
library, we only need a manageable patch set.  Plus, we get the client
tools basically for free.  If we want to distribute them is another
question.

[1] <https://github.com/garyhouston/rxspencer>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant