Hi Scott,

On Mon, Feb 26, 2018 at 11:54 PM, Scott Palmer <[email protected]> wrote:

> That is of course the “correct” way to do this. But I still wonder, why
> doesn’t NetBeans use the standard java launcher that is produced by
> javapackager?
>

I am not sure what exactly is the proposal - could you please share some
more details?

Looking at the current launchers, they seem to provide at least these
services:
-run the updater before or after the IDE/application is run, and possibly
restart the IDE/application after running the updater
-find a viable JDK (or read the path from etc/netbeans.conf)
-read extra options (including VM options) from etc/netbeans.conf
-detect userdir and cache dir locations
-for Windows, the launcher itself probably has an icon

Also, our builds are currently multiplatform (esp. Linux build can run on
Windows), and I think it would be good to keep this.

It we can maintain less platform-specific code, that would be nice, but I
think I'd need a more complete proposal on how to exactly do that without
loosing too many of the above features.

Jan


>
> (If it isn’t good enough, it should be. We should file an issue with the
> JDK if it is inadequate.)
>
> Scott
>
> > On Feb 25, 2018, at 10:00 PM, John Muczynski <[email protected]>
> wrote:
> >
> > Hi guys,
> >
> > At work we commit binaries (products of a build) into a binary repository
> > (Artifactory).
> >
> > In order to bundle them along with the jar files, a Java build then
> fetches
> > these hard-to-build pieces, made by the other build. They are specified
> > with a specific version number by using Maven coordinates.
> >
> > Kind regards,
> > Johnny
> >
> >
> >
> >> On Feb 25, 2018 12:51 AM, "Jan Lahoda" <[email protected]> wrote:
> >>
> >>> On Fri, Feb 23, 2018 at 5:09 PM, Eric Barboni <[email protected]>
> wrote:
> >>>
> >>> Hi Jan,
> >>>
> >>> I try to  make it concrete to me (as I am not sure to understand
> >>> completely the workflow).
> >>>
> >>> We may add a folder to nbbuild/buildnatives that contains all the make
> c
> >>> stuff to compile and release (linked to the source we need for example
> in
> >>> o.n.bootstrap and ide/native)
> >>>
> >>> Phase 1  (optional)
> >>> clone netbeans-incubator and execute the nbbuild/buildnatives
> >>>
> >>
> >> As Emilian noted, not sure if we need another directory. Maybe we could
> >> just have a few special targets in nbbuild/build.xml, that would
> delegate
> >> to appropriate Makefiles.
> >>
> >>
> >>> Phase 2
> >>> clone netbeans-incubator ,ant and use the released native
> >>>
> >>
> >> Yes.
> >>
> >> Overall, I think there are two important things:
> >> -folks building NetBeans shouldn't need to have a C/C++ compiler
> installed
> >> -NetBeans builds should be multi-platform (so that doing a build on
> Linux
> >> gets a binary that can run on Windows)
> >>
> >> There are only very few native components, so overall, this should be
> >> doable.
> >>
> >> Traditionally, we had the launchers checked-in directly in the
> repository,
> >> but that's not allowed in ASF. Hence the idea with releasing launchers
> >> separately. But if there's a better solution, I'm for it.
> >>
> >> Jan
> >>
> >>
> >>> Is it a "possible" workflow ?
> >>>
> >>> Regards
> >>> Eric
> >>>
> >>>
> >>> -----Message d'origine-----
> >>> De : Jan Lahoda [mailto:[email protected]]
> >>> Envoyé : vendredi 23 février 2018 13:10
> >>> À : [email protected]
> >>> Objet : Re: launcher for windows and building c file
> >>>
> >>>> On Fri, Feb 23, 2018 at 1:02 PM, Eric Barboni <[email protected]>
> wrote:
> >>>>
> >>>> Hi,
> >>>> I know that Apache Openoffice use buildbot[1,2] with cygwin on it.
> >>>>
> >>>> We need ask Apache Infra for that. We also need a new repository.
> >>>>
> >>>
> >>> We can definitely ask for a new repository, but do we need one? I.e.
> why
> >>> can't the sources be part of the main repo, and just produce a release
> >> as a
> >>> subset of that repo? (We already do that with the NB platform.)
> >>>
> >>> Jan
> >>>
> >>>
> >>>> Regards
> >>>> Eric
> >>>> [1]
> >>>> https://ci.apache.org/builders/aoo-w741x
> >>>> [2]
> >>>> https://ci.apache.org/buildbot.html
> >>>>
> >>>> -----Message d'origine-----
> >>>> De : Jan Lahoda [mailto:[email protected]] Envoyé : vendredi 23
> février
> >>>> 2018 12:02 À : [email protected] Objet : Re: launcher
> >>>> for windows and building c file
> >>>>
> >>>> On Thu, Feb 22, 2018 at 4:59 PM, Eric Barboni <[email protected]>
> >> wrote:
> >>>>
> >>>>> Hi,
> >>>>> I setup cygwin64 on windows 10. Thanks to your tips I update to
> >>>>> i686* tools chain.
> >>>>> I add to static link libgcc, libstdc++ and also add -static
> >>>>> lpthread to get it works.
> >>>>>
> >>>>> Artefact are huge now but I was able test some code to check for
> >>>>> jdk9 compatibility.
> >>>>>
> >>>>> The remaining issue are:
> >>>>> how  to generate the platform-launcher-9.0beta.zip and
> >>>>> launcher.zip, how to populate the external binaries repository with
> >>>>> those artefact
> >>>>>
> >>>>
> >>>> When I was thinking of this, I was thinking it would be in line with
> >>>> the Apache approach to create a separate release with just the
> >>>> launchers (this wouldn't quite require moving that ouside of the repo,
> >>>> it could be a task to simply pack a piece of the big repo). That would
> >>>> be sources and convenience binaries. Should be reasonably small. And
> >>>> when building the IDE, the convenience binaries for launchers would be
> >>>> downloaded and incorporated to the built IDE. I assume some work will
> >>>> be needed to setup such a release. It would be ideal if the
> >>>> convenience binaries would be uploaded to Maven. Upload to the legacy
> >>>> binary repository requires commit rights to hg.netbeans.org.
> >>>>
> >>>> Are there build machines at Apache that have mingw? It would be
> >>>> definitely good to have an "official" build.
> >>>>
> >>>> Thanks,
> >>>>     Jan
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>> Regards
> >>>>> Eric
> >>>>>
> >>>>>
> >>>>> -----Message d'origine-----
> >>>>> De : John Muczynski [mailto:[email protected]] Envoyé : mercredi
> >>>>> 21 février 2018 19:10 À : [email protected] Objet :
> >>> Re:
> >>>>> launcher for windows and building c file
> >>>>>
> >>>>> Hi Eric,
> >>>>>
> >>>>> These are excellent issues to unearth.
> >>>>> I like the idea of creating a setup to build the executable.
> >>>>>
> >>>>> Here at work, we don't build the launcher too often.
> >>>>> We keep a zip of C:\cygwin from a set of cygwin files that worked to
> >>>>> build the launcher.
> >>>>> I notice that my NetBeans is set up to use
> >>>>> C:\cygwin\bin\i686-w64-mingw32-g++.exe
> >>>>> when building from the IDE.
> >>>>>
> >>>>> You were asking if someone had a working setup. Would more
> >>>>> information and/or files about this process help you personally?
> >>>>>
> >>>>> Kind Regards,
> >>>>> Johnny
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Johnny Muczynski
> >>>>> 734-262-2045
> >>>>>
> >>>>> On Wed, Feb 21, 2018 at 12:54 PM, Eric Barboni <[email protected]>
> >>> wrote:
> >>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>>  I was trying to launch Apache Netbeans 9.0 beta on a windows 10
> >>>>>> box with only jdk9 installed.
> >>>>>>
> >>>>>>  Executable is failing to retrieve a 1.8 or higher java because
> >>>>>> of important registry changes in jdk9 and also version scheme
> >> change
> >>> [2].
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>  I try to follow the wiki page [1] but the required old compiler
> >>>>>> are gone in cygwin. I also give a try to  mingw32 toolchain. No
> >>>>>> luck :/
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Question 1:
> >>>>>>
> >>>>>> Did someone have a working setup for building this ?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Question 2:
> >>>>>>
> >>>>>> Would it be an option to move the windows  “c++” code to another
> >>>>>> git repository ? Setup a Jenkins or buildbot at Apache to build
> >>>>>> the executable in a consistent way.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Best Regards
> >>>>>>
> >>>>>> Eric
> >>>>>>
> >>>>>> [1]
> >>>>>>
> >>>>>> http://wiki.netbeans.org/LauncherBuild
> >>>>>>
> >>>>>> [2]
> >>>>>>
> >>>>>>
> >>>>>> <https://docs.oracle.com/javase/9/install/installation-
> >>>>>> jdk-and-jre-microsoft
> >>>>>> -windows-platforms.htm>
> >>>>>> https://docs.oracle.com/javase/9/install/installation-
> >>>>>> jdk-and-jre-microsoft-
> >>>>>> windows-platforms.htm    ( § Windows Registry Settings)
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --------------------------------------------------------------------
> >>>>> - To unsubscribe, e-mail:
> >>>>> [email protected]
> >>>>> For additional commands, e-mail:
> >>>>> [email protected]
> >>>>>
> >>>>> For further information about the NetBeans mailing lists, visit:
> >>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: [email protected]
> >>>> For additional commands, e-mail:
> >>>> [email protected]
> >>>>
> >>>> For further information about the NetBeans mailing lists, visit:
> >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [email protected]
> >>> For additional commands, e-mail: [email protected].
> apache.org
> >>>
> >>> For further information about the NetBeans mailing lists, visit:
> >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>
> >>>
> >>>
> >>>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Reply via email to