Re: [Build] XCodeLegacy - Re: dmake and epm
With Xcode9, you do need to use Xcodelegacy. > On Oct 25, 2017, at 11:19 AM, Dave Fisher <dave2w...@comcast.net> wrote: > > Hi Jim, > > Thanks. I have Xcode 9 which has the following: > > $ xcodebuild -showsdks > iOS SDKs: > iOS 11.0-sdk iphoneos11.0 > > iOS Simulator SDKs: > Simulator - iOS 11.0-sdk iphonesimulator11.0 > > macOS SDKs: > macOS 10.13 -sdk macosx10.13 > > tvOS SDKs: > tvOS 11.0 -sdk appletvos11.0 > > tvOS Simulator SDKs: > Simulator - tvOS 11.0 -sdk appletvsimulator11.0 > > watchOS SDKs: > watchOS 4.0 -sdk watchos4.0 > > watchOS Simulator SDKs: > Simulator - watchOS 4.0 -sdk watchsimulator4.0 > > I modified configure to target 10.13 and adjusted the egrep: > > sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | sed > -e "s/.*sdk //" | head -n1` > > Also - > # sdk_target=10.9 > > >sdk_target=10.13 > > The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the > release script is not used. > > On to the next issue with the category B downloads. Certificate store issues > giving 500 errors. > > Also, I noticed a version 5.5 of Tomcat …. > > Regards, > Dave > >> On Oct 25, 2017, at 5:32 AM, Jim Jagielski <j...@jagunet.com >> <mailto:j...@jagunet.com>> wrote: >> >> Actually, if you have Xcode7 or Xcode8, there is no need for >> Xcodelegacy at all. >> >> All Xcodelegacy does is obtain older macOS SDKs and installs them >> in Xcode. But we use the latest SDK available (via configure). So >> Xcodelegacy is not a requirement/dependency per se. It's just >> useful in case we get into a situation where we need to >> use an older SDK rather than the latest. >> >>> On Oct 24, 2017, at 6:00 PM, Dave Fisher <dave2w...@comcast.net >>> <mailto:dave2w...@comcast.net>> wrote: >>> >>> Hi Jim, >>> >>> I’m hung up on what I should do with >>> https://github.com/devernay/xcodelegacy >>> <https://github.com/devernay/xcodelegacy> >>> <https://github.com/devernay/xcodelegacy >>> <https://github.com/devernay/xcodelegacy>> >>> >>> What should I download before I run the scripts? Which form of the command >>> should I use? >>> >>> BTW - this requirement is only mentioned in the build release script. >>> >>> Regards, >>> Dave >>> >>>> On Oct 23, 2017, at 5:38 PM, Dave Fisher <dave2w...@comcast.net >>>> <mailto:dave2w...@comcast.net> <mailto:dave2w...@comcast.net >>>> <mailto:dave2w...@comcast.net>>> wrote: >>>> >>>> Hi Jim, >>>> >>>> I wanted to validate build instructions. Should I take these two from your >>>> github for my MacOS Sierra environment? >>>> >>>> Regards, >>>> Dave >>>> >>>> Sent from my iPhone >>>> >>>>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com >>>>> <mailto:j...@jagunet.com> <mailto:j...@jagunet.com >>>>> <mailto:j...@jagunet.com>>> wrote: >>>>> >>>>> Just a FYI that I am tracking dmake and epm on the >>>>> below Github pages: >>>>> >>>>> o https://github.com/jimjag/epm <https://github.com/jimjag/epm> >>>>> <https://github.com/jimjag/epm <https://github.com/jimjag/epm>> >>>>> o https://github.com/jimjag/dmake <https://github.com/jimjag/dmake> >>>>> <https://github.com/jimjag/dmake <https://github.com/jimjag/dmake>> >>>>> >>>>> I know we are moving away from dmake, but IMO it'll take >>>>> some time for that to be complete. Plus, updating to the >>>>> latest version of EPM is useful (it's the ONLY way to build >>>>> the macOS versions now, for example), but we also need >>>>> the AOO-specific patches in there. Which are included >>>>> in my forks. >>>>> >>>>> Just topic for discussion and chewing over >>>>> >>>>> - >>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>> <mailto:dev-unsubscr...@openoffice.apache.org> >>>>> <mailto:dev-unsubscr...@openoffice.apache.org >>>>> <mailto:dev-unsubscr...@openoffice.apache.org>> >>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>> <mailto:dev-h...@openoffice.apache.org> >>>>> <mailto:dev-h...@openoffice.apache.org >>>>> <mailto:dev-h...@openoffice.apache.org>> >>>>> >>>> >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> <mailto:dev-unsubscr...@openoffice.apache.org> >>>> <mailto:dev-unsubscr...@openoffice.apache.org >>>> <mailto:dev-unsubscr...@openoffice.apache.org>> >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> <mailto:dev-h...@openoffice.apache.org> >>>> <mailto:dev-h...@openoffice.apache.org >>>> <mailto:dev-h...@openoffice.apache.org>> >>>> >>> >> >
Re: dmake and epm
Hi - FYI - on https://sourceforge.net/projects/oooextras.mirror/files/ <https://sourceforge.net/projects/oooextras.mirror/files/> The epm version there is 3.7. It can be configured as: configure:1952: --disable-epm AOO includes self-packaging code, that requires configure:1953: epm, however epm is useless for large scale configure:2218: --with-epm Decides which epm to use. Default is to use configure:2221: epm will be built. configure:2223: --with-epm-url=Specify the location of downloadable epm source code. For example: configure:2224: https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz configure:2226: http://epm.sourcearchive.com/downloads/3.7-1/epm_3.7.orig.tar.gz configure:2227: Version 3.7 or later is required. Note that epm is under GPL license. Any reason to make changes in configure, or should we warn? Regards, Dave > On Oct 25, 2017, at 5:34 AM, Jim Jagielski <j...@jagunet.com> wrote: > > You can. I used the downloads mentioned in the macOS build script > for AOO414. > > The version of dmake isn't important. The version of epm *is* > (it must be 4.3 or later) because it allows for direct building > of dmg's w/o requiring a long deprecated support application > which is no longer available. > >> On Oct 23, 2017, at 8:38 PM, Dave Fisher <dave2w...@comcast.net> wrote: >> >> Hi Jim, >> >> I wanted to validate build instructions. Should I take these two from your >> github for my MacOS Sierra environment? >> >> Regards, >> Dave >> >> Sent from my iPhone >> >>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com> wrote: >>> >>> Just a FYI that I am tracking dmake and epm on the >>> below Github pages: >>> >>> o https://github.com/jimjag/epm >>> o https://github.com/jimjag/dmake >>> >>> I know we are moving away from dmake, but IMO it'll take >>> some time for that to be complete. Plus, updating to the >>> latest version of EPM is useful (it's the ONLY way to build >>> the macOS versions now, for example), but we also need >>> the AOO-specific patches in there. Which are included >>> in my forks. >>> >>> Just topic for discussion and chewing over >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > signature.asc Description: Message signed with OpenPGP
Re: [Build] XCodeLegacy - Re: dmake and epm
Hi Jim, Thanks. I have Xcode 9 which has the following: $ xcodebuild -showsdks iOS SDKs: iOS 11.0-sdk iphoneos11.0 iOS Simulator SDKs: Simulator - iOS 11.0-sdk iphonesimulator11.0 macOS SDKs: macOS 10.13 -sdk macosx10.13 tvOS SDKs: tvOS 11.0 -sdk appletvos11.0 tvOS Simulator SDKs: Simulator - tvOS 11.0 -sdk appletvsimulator11.0 watchOS SDKs: watchOS 4.0 -sdk watchos4.0 watchOS Simulator SDKs: Simulator - watchOS 4.0 -sdk watchsimulator4.0 I modified configure to target 10.13 and adjusted the egrep: sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | sed -e "s/.*sdk //" | head -n1` Also - # sdk_target=10.9 sdk_target=10.13 The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the release script is not used. On to the next issue with the category B downloads. Certificate store issues giving 500 errors. Also, I noticed a version 5.5 of Tomcat …. Regards, Dave > On Oct 25, 2017, at 5:32 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Actually, if you have Xcode7 or Xcode8, there is no need for > Xcodelegacy at all. > > All Xcodelegacy does is obtain older macOS SDKs and installs them > in Xcode. But we use the latest SDK available (via configure). So > Xcodelegacy is not a requirement/dependency per se. It's just > useful in case we get into a situation where we need to > use an older SDK rather than the latest. > >> On Oct 24, 2017, at 6:00 PM, Dave Fisher <dave2w...@comcast.net> wrote: >> >> Hi Jim, >> >> I’m hung up on what I should do with https://github.com/devernay/xcodelegacy >> <https://github.com/devernay/xcodelegacy> >> >> What should I download before I run the scripts? Which form of the command >> should I use? >> >> BTW - this requirement is only mentioned in the build release script. >> >> Regards, >> Dave >> >>> On Oct 23, 2017, at 5:38 PM, Dave Fisher <dave2w...@comcast.net >>> <mailto:dave2w...@comcast.net>> wrote: >>> >>> Hi Jim, >>> >>> I wanted to validate build instructions. Should I take these two from your >>> github for my MacOS Sierra environment? >>> >>> Regards, >>> Dave >>> >>> Sent from my iPhone >>> >>>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com >>>> <mailto:j...@jagunet.com>> wrote: >>>> >>>> Just a FYI that I am tracking dmake and epm on the >>>> below Github pages: >>>> >>>> o https://github.com/jimjag/epm <https://github.com/jimjag/epm> >>>> o https://github.com/jimjag/dmake <https://github.com/jimjag/dmake> >>>> >>>> I know we are moving away from dmake, but IMO it'll take >>>> some time for that to be complete. Plus, updating to the >>>> latest version of EPM is useful (it's the ONLY way to build >>>> the macOS versions now, for example), but we also need >>>> the AOO-specific patches in there. Which are included >>>> in my forks. >>>> >>>> Just topic for discussion and chewing over >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> <mailto:dev-unsubscr...@openoffice.apache.org> >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> <mailto:dev-h...@openoffice.apache.org> >>>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> <mailto:dev-unsubscr...@openoffice.apache.org> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> <mailto:dev-h...@openoffice.apache.org> >>> >> > signature.asc Description: Message signed with OpenPGP
Re: dmake and epm
You can. I used the downloads mentioned in the macOS build script for AOO414. The version of dmake isn't important. The version of epm *is* (it must be 4.3 or later) because it allows for direct building of dmg's w/o requiring a long deprecated support application which is no longer available. > On Oct 23, 2017, at 8:38 PM, Dave Fisher <dave2w...@comcast.net> wrote: > > Hi Jim, > > I wanted to validate build instructions. Should I take these two from your > github for my MacOS Sierra environment? > > Regards, > Dave > > Sent from my iPhone > >> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com> wrote: >> >> Just a FYI that I am tracking dmake and epm on the >> below Github pages: >> >> o https://github.com/jimjag/epm >> o https://github.com/jimjag/dmake >> >> I know we are moving away from dmake, but IMO it'll take >> some time for that to be complete. Plus, updating to the >> latest version of EPM is useful (it's the ONLY way to build >> the macOS versions now, for example), but we also need >> the AOO-specific patches in there. Which are included >> in my forks. >> >> Just topic for discussion and chewing over >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build] XCodeLegacy - Re: dmake and epm
Actually, if you have Xcode7 or Xcode8, there is no need for Xcodelegacy at all. All Xcodelegacy does is obtain older macOS SDKs and installs them in Xcode. But we use the latest SDK available (via configure). So Xcodelegacy is not a requirement/dependency per se. It's just useful in case we get into a situation where we need to use an older SDK rather than the latest. > On Oct 24, 2017, at 6:00 PM, Dave Fisher <dave2w...@comcast.net> wrote: > > Hi Jim, > > I’m hung up on what I should do with https://github.com/devernay/xcodelegacy > <https://github.com/devernay/xcodelegacy> > > What should I download before I run the scripts? Which form of the command > should I use? > > BTW - this requirement is only mentioned in the build release script. > > Regards, > Dave > >> On Oct 23, 2017, at 5:38 PM, Dave Fisher <dave2w...@comcast.net >> <mailto:dave2w...@comcast.net>> wrote: >> >> Hi Jim, >> >> I wanted to validate build instructions. Should I take these two from your >> github for my MacOS Sierra environment? >> >> Regards, >> Dave >> >> Sent from my iPhone >> >>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com >>> <mailto:j...@jagunet.com>> wrote: >>> >>> Just a FYI that I am tracking dmake and epm on the >>> below Github pages: >>> >>> o https://github.com/jimjag/epm <https://github.com/jimjag/epm> >>> o https://github.com/jimjag/dmake <https://github.com/jimjag/dmake> >>> >>> I know we are moving away from dmake, but IMO it'll take >>> some time for that to be complete. Plus, updating to the >>> latest version of EPM is useful (it's the ONLY way to build >>> the macOS versions now, for example), but we also need >>> the AOO-specific patches in there. Which are included >>> in my forks. >>> >>> Just topic for discussion and chewing over >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> <mailto:dev-unsubscr...@openoffice.apache.org> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> <mailto:dev-h...@openoffice.apache.org> >>> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> <mailto:dev-unsubscr...@openoffice.apache.org> >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> <mailto:dev-h...@openoffice.apache.org> >> >
[Build] XCodeLegacy - Re: dmake and epm
Hi Jim, I’m hung up on what I should do with https://github.com/devernay/xcodelegacy <https://github.com/devernay/xcodelegacy> What should I download before I run the scripts? Which form of the command should I use? BTW - this requirement is only mentioned in the build release script. Regards, Dave > On Oct 23, 2017, at 5:38 PM, Dave Fisher <dave2w...@comcast.net> wrote: > > Hi Jim, > > I wanted to validate build instructions. Should I take these two from your > github for my MacOS Sierra environment? > > Regards, > Dave > > Sent from my iPhone > >> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com> wrote: >> >> Just a FYI that I am tracking dmake and epm on the >> below Github pages: >> >> o https://github.com/jimjag/epm >> o https://github.com/jimjag/dmake >> >> I know we are moving away from dmake, but IMO it'll take >> some time for that to be complete. Plus, updating to the >> latest version of EPM is useful (it's the ONLY way to build >> the macOS versions now, for example), but we also need >> the AOO-specific patches in there. Which are included >> in my forks. >> >> Just topic for discussion and chewing over >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > signature.asc Description: Message signed with OpenPGP
Re: dmake and epm
Hi Jim, I wanted to validate build instructions. Should I take these two from your github for my MacOS Sierra environment? Regards, Dave Sent from my iPhone > On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Just a FYI that I am tracking dmake and epm on the > below Github pages: > > o https://github.com/jimjag/epm > o https://github.com/jimjag/dmake > > I know we are moving away from dmake, but IMO it'll take > some time for that to be complete. Plus, updating to the > latest version of EPM is useful (it's the ONLY way to build > the macOS versions now, for example), but we also need > the AOO-specific patches in there. Which are included > in my forks. > > Just topic for discussion and chewing over > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
dmake and epm
Just a FYI that I am tracking dmake and epm on the below Github pages: o https://github.com/jimjag/epm o https://github.com/jimjag/dmake I know we are moving away from dmake, but IMO it'll take some time for that to be complete. Plus, updating to the latest version of EPM is useful (it's the ONLY way to build the macOS versions now, for example), but we also need the AOO-specific patches in there. Which are included in my forks. Just topic for discussion and chewing over - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
