Re: [Gimp-print-devel] RFC: New release and abandoning MacOS?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

> On Aug 8, 2024, at 6:52 AM, Greg Troxel <gd...@le...> wrote:
> 
> Matt Broughton <wal...@ma...> writes:
> 
>>> On Aug 7, 2024, at 6:53 AM, Greg Troxel <gd...@le...> wrote:
>>> 
>>> Matt Broughton <wal...@ma...> writes:
>>> 
>>>> The third party package managers for macos are fink, mac ports, and
>>>> brew.  One of them might be interested.  I have used all three of them
>>>> at one point or another.
>>> 
>>> pkgsrc also builds for macos, among many others.
>> 
>> Thanks for the information Greg.  Somehow I missed that resource.
>> 
>> The nice thing about using a package manager for macos is that the
>> package maintainer will make sure that libusb is available.  All of
>> the existing macos v5.3.x packages break Solomon's backend because
>> libusb was not built against the static library.  My attempts to build
>> against a static libusb have failed.  From searching the web, there
>> seems to be little, if any, real support for building against static
>> libraries.
>> Matt
> 
> I am not quite following.  Are you trying to build a gutenprint dynamic
> library that has somehow included ilbusb?   I don't understand why you
> would need to do this, but I'm used to a world where all the instsalled
> libraries are ok.

Sorry about not being clear -- part stream of consciousness and part not fully knowing what I am doing.

libusb is not included with any version of macos. What I am tyring to do is make an installer package for Gutenprint where gutenprint53+usb will work without having the macos Gutenprint installer actually installing libusb--  to build a statically linked binary or library.

There are a couple of reasons for this.  1. I don't want to have to worry about license compatibility, distributing a copy of libusb license, source code etc.    2. The end user may already have libusb installed and I sure don't want to clobber it. Steps can be taken to get around this, but things get more complicated and the 'uninstaller' must also be updated carefully so that it only removes files and symlinks Gutennprint installed.

Matt