kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #17143
Re: USE_OSX_DEPS_BUILDER
I was suspecting that.
Another hint for distro
to finish better the work could be nice to put all directories that in linux is under
/usr/share/kicad/internat/ into kicad.app/Contents/Resources/
Having something like:
kicad.app/Contents/Resources/<nation>/kicad.mo
kicad.app/Contents/Resources/<nation>/kicad.po
then simbolic link directories them under the bundled applications,
having something like:
kicad.app/Contents/Applications/<application>.app/Contents/Resources/<language>/kicad.mo
This will provide translations for all languages like other platforms keep saving diskspace.
I’ve tested the translations successfully time ago and i think should still work.
PS.
Please make a i386 binary once each 6 months, i have an old mini that still kicking ;)
—
Marco
> On 01/mar/2015, at 03:52, Garth Corral <gcorral@xxxxxxxxx> wrote:
>
> The libX dylibs are not needed. The library dependencies can and should be built without X.
> If the kicad binaries are not 2-way fat then there’s no reason the bundled libs should be either.
>
> Garth
>
>> On Feb 28, 2015, at 3:18 PM, Marco Serantoni <marco.serantoni@xxxxxxxxx> wrote:
>>
>> Wayne,
>> At the time we were in a timeframe where was ppc finishing his fading out, i386 in mid term, x86_64 was not already fully adopted.
>> KiFace work begin was forcing a migration from the old default behavior of static linking to dynamic.
>> Now:
>> i386 fading/faded out completely.
>> The linking is dynamic.
>> All bundles are collapsed to a single one after KiFace become complete.
>>
>> So i386 could be desupported, the issue of multiple copies of dynamic libraries for each bundle, as planned, is no more needed too.
>> I personally think that also Phyton could be now migrated to 2.7 and no more 2.6 (other legacy from the platforms above).
>>
>> Much of that work is now obsolete.
>> Guys has done a great job with the new disto.
>>
>> I’ve a couple of question for them:
>> * Are libX*.dynlib really needed ?
>> * Since binaries are x86_64, do you think isn’t the case to use “lipo -remove” for unneeded architecture from all dynlibs?
>>
>> Great job!
>>
>> —
>> Marco
>>
>>> On 25/feb/2015, at 22:52, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>>
>>> I'm surprised it still works with all of the changes made for the OSX
>>> bundle support. I'll leave it as is for the upcoming stable release.
>>> Please take note that one of the first things I'm going to do after the
>>> stable release is remove all of the download_foo code from the kicad
>>> build system. This code should have always been maintained outside the
>>> kicad source tree as a stand alone project or projects if you would
>>> prefer one project per dependency. Everyone has plenty of warning so if
>>> you depend on this to build dependencies on your platform, now is the
>>> time to start working on what ever dependency builders you need.
>>>
>>> On 2/25/2015 1:47 PM, Garth Corral wrote:
>>>> I do use it but I'm not opposed to removing it if that's what you want.
>>>> It does still seem to work and is convenient if you don't want to use
>>>> installed dependencies. I can just as easily move that to a script, though.
>>>>
>>>> Garth
>>>>
>>>> On Feb 25, 2015, at 10:30 AM, Bernhard Stegmaier
>>>> <stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>> wrote:
>>>>
>>>>> No, I didn’t use it since the app bundle updates.
>>>>> I even don’t know if it still works with all the changes since.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Bernhard
>>>>>
>>>>>> On 25 Feb 2015, at 18:47, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx
>>>>>> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>> wrote:
>>>>>>
>>>>>> The nightlies do not.
>>>>>>
>>>>>> Adam Wolf
>>>>>>
>>>>>> On Wed, Feb 25, 2015 at 11:29 AM, Wayne Stambaugh
>>>>>> <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>> wrote:
>>>>>>
>>>>>> Is anyone still using the old USE_OSX_DEPS_BUILDER? If not, I think
>>>>>> it's time to remove it from CMakeLists.txt.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Wayne
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References