[omniORB] Building omniorb against openssl 3.6.5

Duncan Grisby duncan at grisby.org
Thu Oct 22 13:56:53 UTC 2026


On Tue, 2026-10-20 at 09:51 +0200, Daniel Krügler via omniORB-list
wrote:

[...]
> shared\omnisslTP4.def(1) : warning LNK4093: Drive/Directory component
> ignored in 'LIBRARY' statement
>    Creating library shared/omnisslTP434_rt.lib and object
> shared/omnisslTP434_rt.exp
> libcrypto.lib(libcrypto-lib-e_capi.obj) : error LNK2019: unresolved
> external symbol __imp_CertOpenStore referenced in function
> capi_open_store

[...]

> Notice that the created command line does *not* list crypt32.lib
> (whose absence is the cause of above linkage errors), albeit I
> defined

Where did your OpenSSL build come from?  The one from
https://slproweb.com/products/Win32OpenSSL.html does not have a
dependency on crypt32.lib.


> OPEN_SSL_LIB = $(patsubst %,$(LibPathPattern),$(OPEN_SSL_ROOT)/lib) \
>                libssl.lib libcrypto.lib
> OMNIORB_SSL_LIB += $(OPEN_SSL_LIB) user32.lib crypt32.lib ws2_32.lib
> bcrypt.lib
> 
> in my x86_win32_vs_143_64.mk. 
> 
> It seems as if the variable  OMNIORB_SSL_LIB is not properly
> considered for the build of  omnisslTP434_rt.lib. For testing
> purposes I instead expanded  OPEN_SSL_LIB as follows

It is not very well explained in the makefiles, but OMNIORB_SSL_LIB is
used for programs that link with the omniORB SSL transport — it is not
used when linking the omnisslTP library itself.

> OPEN_SSL_LIB = $(patsubst %,$(LibPathPattern),$(OPEN_SSL_ROOT)/lib) \
>                libssl.lib libcrypto.lib \
>                crypt32.lib bcrypt.lib ws2_32.lib user32.lib
> advapi32.lib

That is the correct define that is used when building the SSL
transport, so it is the correct place to add any dependant libraries.

Duncan.

-- 
Duncan Grisby <duncan at grisby.org>



More information about the omniORB-list mailing list