[ 
https://issues.apache.org/jira/browse/XERCESC-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeroen updated XERCESC-2167:
----------------------------
    Description: 
 

{{When building a static library (i.e. building with cmake 
-DBUILD_SHARED_LIBS=OFF`, we should not set a SONAME or rename the library 
file. A static library should just be named libxerces-c.a and not 
libxerces-c-3.2.a (otherwise it won't link with -lxerces-c).}}

Here is a very simple example patch: 
[https://patch-diff.githubusercontent.com/raw/jeroen/xerces-c/pull/1.patch]

 

Thank you!

  was:
 

When building a static library (i.e. building with `cmake 
-DBUILD_SHARED_LIBS=OFF`), we should not set a SONAME or rename the library 
file. A static library should just be named libxerces-c.a and not 
libxerces-c-3.2.a (otherwise it won't link with -lxerces-c).

Here is a very simple example patch: 
[https://patch-diff.githubusercontent.com/raw/jeroen/xerces-c/pull/1.patch]

 

Thank you!


> Do not set SONAME when building shared libs
> -------------------------------------------
>
>                 Key: XERCESC-2167
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2167
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.2.2
>            Reporter: Jeroen
>            Priority: Major
>
>  
> {{When building a static library (i.e. building with cmake 
> -DBUILD_SHARED_LIBS=OFF`, we should not set a SONAME or rename the library 
> file. A static library should just be named libxerces-c.a and not 
> libxerces-c-3.2.a (otherwise it won't link with -lxerces-c).}}
> Here is a very simple example patch: 
> [https://patch-diff.githubusercontent.com/raw/jeroen/xerces-c/pull/1.patch]
>  
> Thank you!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to