• Tor Lillqvist's avatar
    Handle lack of module loading/unloading API when DISABLE_DYNLOADING · 97593ae2
    Tor Lillqvist yazdı
    There are basicically two classes of cases:
    
    1) Where the code is for obscure historical reasons or what I see as
    misguided "optimization" split into a more libraries than necessary,
    and these then are loaded at run-time. Instead, just use direct
    linking.
    
    2) Where dynamic loading is part of the functionality offered to some
    upper (scripting etc) layer, or where some system-specific non-LO
    library is loaded dynamically, as it is not necessarily present on
    end-user machines. Can't have such in the DISABLE_DYNLOADING case.
    
    Change-Id: I9eceac5fb635245def2f4f3320821447bb7cd8c0
    97593ae2
Adı
Son kayıt (commit)
Son güncelleme
..
inc Loading commit data...
prj Loading commit data...
qa Loading commit data...
source Loading commit data...
util Loading commit data...
CppunitTest_cppu_checkapi.mk Loading commit data...
CppunitTest_cppu_qa_any.mk Loading commit data...
CppunitTest_cppu_qa_recursion.mk Loading commit data...
CppunitTest_cppu_qa_reference.mk Loading commit data...
CppunitTest_cppu_qa_unotype.mk Loading commit data...
CppunitTest_cppu_test_cppumaker.mk Loading commit data...
CustomTarget_cppu_allheaders.mk Loading commit data...
InternalUnoApi_cppu.mk Loading commit data...
Library_affine_uno.mk Loading commit data...
Library_cppu.mk Loading commit data...
Library_log_uno.mk Loading commit data...
Library_purpenvhelper.mk Loading commit data...
Library_unsafe_uno.mk Loading commit data...
Makefile Loading commit data...
Module_cppu.mk Loading commit data...
Package_inc.mk Loading commit data...
README Loading commit data...