Welcome to xmlsec Discussions!

[lsh123]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[jefmason]

I work at Siemens with a number of 'legacy' C/C++ applications that use openssl/xmlsec. I am currently involved in evaluating a port to openssl3. My involvement is to use existing functionality in these packages moving into the future

[jefmason]

I just noticed that xmlsec does not release the xmlsec/openssl include files when only a static library is built on windows. I modified the win32 Makefile.msvc to add targets to create this directory and populate it when $(BINDIR)$(XMLSEC_OPENSSL_A) exists. I now get these files released in my build and can use them. I did not modify any other targets like uninstall, only the install target. I believe this is the correct solution to an oversight.

[lsh123]

could you please create an issue on github and if possible share your changes as a PR?

[jefmason]

I am new to filing things in github so will attempt to do this. Thanks. From: lsh123 ***@***.***> Sent: Tuesday, October 25, 2022 11:02 AM To: lsh123/xmlsec ***@***.***> Cc: jefmason ***@***.***>; Comment ***@***.***> Subject: Re: [lsh123/xmlsec] Welcome to xmlsec Discussions! (Discussion #409) could you please create an issue on github and if possible share your changes as a PR? — Reply to this email directly, view it on GitHub<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flsh123%2Fxmlsec%2Fdiscussions%2F409%23discussioncomment-3962552&data=05%7C01%7C5808d477-50c4-446f-bb12-a3337d0f7c1b%40ad011.siemens.com%7C2c18764331244e9931ff08dab6aa98a8%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638023141065632120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rVl0HJGWmiMzR0tPD76j4yO5KVvmoOk40DWOP%2BlFrDg%3D&reserved=0>, or unsubscribe<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA32DFOITOHDVCK5ZC3T2IG3WFAG7PANCNFSM6AAAAAARNMM6II&data=05%7C01%7C5808d477-50c4-446f-bb12-a3337d0f7c1b%40ad011.siemens.com%7C2c18764331244e9931ff08dab6aa98a8%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638023141065632120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GOi8%2F%2F%2FcYJEJv2hAbrsrTpkMbDJ0Uxwos8y6f72oc1o%3D&reserved=0>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[postboy]

For the history purposes: this discussion continued in #420.

[bernardohoehl-web]

Hello! I have a Mac Os X app that uses XMLSEC library to sign an xml string using a p12 certificate. It is old code and still uses xmlsec1-1.2.20. I am having 32 Xcode build errors related to xmlsec library, and so I would like to update my XMLSEC Library used to newest Apple M* (ARM64 or AArch64) chips. I am willing to hire a more experienced programmer willing to help me. Can you help me compile XMLSEC Library to the newest Apple's chips?

[lsh123]

OSX builds are part of XMLSec commit checks so it should “just work”:

https://github.com/lsh123/xmlsec/actions/runs/19788968992/job/56699348014

Build steps:

https://github.com/lsh123/xmlsec/blob/master/.github/workflows/make-check.yml#L108

[lsh123]

Actually, just use homebrew:

1/ install brew: https://brew.sh/

2/ install dependencies and xmlsec:

brew upgrade

brew install libxml2 libxslt
brew install openssl
brew install libxmlsec1