#67 Build install doesn't install static libraries

v2.3.2
closed-fixed
5
2008-01-18
2007-10-23
No

When building the static libraries, it doesn't seem that 'Build install' actually installs the .a's.

When building as shared libraries, it _does_ install the .so's, however.

If you compare the difference between the install-libdkim: Makefile target, you'll see there's extra code to install the .so when building 'sharedlib' that doesn't exist when building 'library'

Discussion

  • Anonymous - 2007-10-23
    • priority: 5 --> 3
    • assigned_to: nobody --> sm-msk
     
  • Anonymous - 2007-10-23

    Logged In: YES
    user_id=1048957
    Originator: NO

    Referred to the devtools guys at Sendmail.

     
  • Anonymous - 2007-10-24

    Logged In: YES
    user_id=1048957
    Originator: NO

    According to one of our devtools maintainers:

    If you build shared libraries, the resulting binaries need the shared
    library to run, hence it is installed. Static libraries are not needed
    by the binaries, therefore not installed. Of course, you can override
    this in your libdkim/Makefile.m4 with:

    define(`bldINSTALLABLE', `true')

    ...inside the bldPRODUCT_START() section.

    Ideally libdkim should be compiled but not installed unless you do "sh Build install" explicitly in the libdkim directory, because then you want the developer stuff installed on your system (the library and dkim.h). I'll see if that's workable with the current system.

     
  • Anonymous - 2008-01-11

    Logged In: YES
    user_id=1048957
    Originator: NO

    A hook to make the library installable via site.config.m4 has been added and will appear in the next version.

     
  • Anonymous - 2008-01-11
    • priority: 3 --> 5
     
  • Anonymous - 2008-01-18
    • status: open --> closed-fixed
     
  • Anonymous - 2008-01-18

    Logged In: YES
    user_id=1048957
    Originator: NO

    v2.4.3, now released, contains a build-time option to deal with this.

     

Log in to post a comment.