Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Thanks Matthias for kicking off the votes on the revised artefacts. I've updated both WIP pull requests, which will build a dev-build with the newly staged binaries as well as tests. I want to double-check on the M1 mac that everything is working before voting, but everything else looks good. https://github.com/apache/netbeans/pull/6502 https://github.com/apache/netbeans/pull/6521 I thought we'd need to filter out the notice and license from the profiler libs, but actually they're already skipped. However, did need adding to the gitignore. On Tue, 10 Oct 2023 at 12:39, Neil C Smith wrote: > Incidentally, IMO let's make the version - > > 1-r24aefa9 (as before) or 1-24aefa9 We need to pick one! The folder uses the "r" prefix, and the file doesn't. They should match. In hindsight I think without the "r" is better. Either way, please make sure they match when svn mv them to release after the vote. Also, on the readme file that Antonio and Eric picked up - the source files are purely a subsection of the IDE sources - that file has been without a header in every IDE release we've had. Does rat ignore .txt files by default? Or am I missing the filter that's allowing it through? Either way I don't think it needs one anyway. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Sun, 8 Oct 2023 at 15:48, Matthias Bläsing wrote: > Am Mittwoch, dem 04.10.2023 um 20:44 +0100 schrieb Neil C Smith: > > If the vote doesn't pass then someone else will need to do the > > various PRs (I'm tied up most of next week), or we delay freeze, or > > we have another release without Apple Silicon support? > > I'm willing to give releasing the native artifacts a try. > > So would you be willing to close the first set of votes? Then I would > call a vote on: > > 1-24aefa99e4f366699431e3e85e6b1127e966a151 > > That is the release, that holds the merge of the modified built. Thanks Matthias. Votes are closed properly and I've unstaged the previous artefacts. A complete change of plan for me this week due to a return visit from the lovely Mr Corona means I will be near both the machine with my signing keys and an M1 Mac. Can test these, or handle some things if needed. Let me know. Incidentally, IMO let's make the version - 1-r24aefa9 (as before) or 1-24aefa9 The 7 character hash as shown on the workflow summary should be fine, and the resulting urls are long enough already (given hash will be in path twice)? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi Neil, Am Mittwoch, dem 04.10.2023 um 20:44 +0100 schrieb Neil C Smith: > If the vote doesn't pass then someone else will need to do the > various PRs (I'm tied up most of next week), or we delay freeze, or > we have another release without Apple Silicon support? I'm willing to give releasing the native artifacts a try. So would you be willing to close the first set of votes? Then I would call a vote on: 1-24aefa99e4f366699431e3e85e6b1127e966a151 That is the release, that holds the merge of the modified built. Greetings Matthias - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, so being constructive about this, I put this together: https://github.com/apache/netbeans/pull/6539 I think my concerns are addressed by that. Greetings Matthias Am Mittwoch, dem 04.10.2023 um 20:44 +0100 schrieb Neil C Smith: > On Wed, 4 Oct 2023, 20:07 Matthias Bläsing, > wrote: > > > I was asked to reply here: > > > > I'm irritated, that votes are called for packages, that violate Apache > > Release requirements (at least to my understanding). > > > > I will not vote on dlight.nativeexecution as I assume the reaction will > > also be just a shrug. The question that remains: Why call a vote then? > > > > So we can host the binaries on dist.a.o rather than the far worse shadow > releasing via OSUOSL that was used for the last update. > > I'm sorry you're irritated by this, but understand it. I made a judgement > call to keep the binary artefact contents the same for this first trial. > This causes a minor violation of the release policy on convenience > binaries, I realise, even though not really public facing. I wish I'd > realised that earlier! It is still far less of one than putting them on > OSUOSL in my opinion. It is at least a step in the right direction. > > The actual voting artefact (source) is compliant, if the contents are a > little odd at present. Again, it was a judgement call to try this with the > workflow without changing too much in the module itself. > > Both things need addressing in the NB21 cycle if this works for us. It's on > my to-do list already leading on from this. > > If the vote doesn't pass then someone else will need to do the various PRs > (I'm tied up most of next week), or we delay freeze, or we have another > release without Apple Silicon support? > > I'm a little irritated with myself for not foreseeing this problem. > Hindsight is great, sorry! > > Best wishes, > > Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Thu, 5 Oct 2023, 21:23 Laszlo Kishalmi, wrote: > > On 10/5/23 12:57, Neil C Smith wrote: > > On Thu, 5 Oct 2023, 19:51 Laszlo Kishalmi, > > wrote: > > > >> Just a question, as the vote has been pulled off. > >> > >> Is it possible to create the binaries cross compile the profiler library > >> on Linux? > >> > > Not sure. No or with difficulty maybe. > > > > What problem would that solve though? Do we expect everyone who builds or > > votes on NetBeans to only do so on Linux with a cross-compiler set up? > > Well back then, I made the windows launchers compiled from the code > using cross compiler. I would not say that is a Linux only option as gnu > c and mingw is available on other platforms as well. However I do not > have other platforms around. > > > https://github.com/apache/netbeans/blob/12.0/README.md#building-windows-launchers Yes, sure. The question is whether we make that a requirement for everyone building the source and stop shipping convenience native binaries at all? Personally, I think that opens up more problems than it solves. Best wishes, Neil
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On 10/5/23 12:57, Neil C Smith wrote: On Thu, 5 Oct 2023, 19:51 Laszlo Kishalmi, wrote: Just a question, as the vote has been pulled off. Is it possible to create the binaries cross compile the profiler library on Linux? Not sure. No or with difficulty maybe. What problem would that solve though? Do we expect everyone who builds or votes on NetBeans to only do so on Linux with a cross-compiler set up? Well back then, I made the windows launchers compiled from the code using cross compiler. I would not say that is a Linux only option as gnu c and mingw is available on other platforms as well. However I do not have other platforms around. https://github.com/apache/netbeans/blob/12.0/README.md#building-windows-launchers If we don't expect all people building our sources to cross-compile all natives, then our problem is more about agreeing how we release natives to then be consumed by anyone building the IDE from the main source bundle. OSUOSL isn't the place to host these for multiple reasons, and any other option is going to need a vote. With all the added benefits of that process (ASF archived, signed, verified, linked sources and binaries, etc.) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Thu, 5 Oct 2023, 19:51 Laszlo Kishalmi, wrote: > Just a question, as the vote has been pulled off. > > Is it possible to create the binaries cross compile the profiler library > on Linux? > Not sure. No or with difficulty maybe. What problem would that solve though? Do we expect everyone who builds or votes on NetBeans to only do so on Linux with a cross-compiler set up? If we don't expect all people building our sources to cross-compile all natives, then our problem is more about agreeing how we release natives to then be consumed by anyone building the IDE from the main source bundle. OSUOSL isn't the place to host these for multiple reasons, and any other option is going to need a vote. With all the added benefits of that process (ASF archived, signed, verified, linked sources and binaries, etc.) Best wishes, Neil
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Just a question, as the vote has been pulled off. Is it possible to create the binaries cross compile the profiler library on Linux? On 9/27/23 03:54, Neil C Smith wrote: Hi, The lack of native binaries supporting Apple Silicon (eg. profiler and terminal) is becoming more and more of an issue, and costing us users. I assume that is something we wish to address?! And incidentally, while we're at it, if you're a NetBeans PMC member or committer using it on macOS regularly on either Apple silicon or x86_64, your input and testing through this would be very appreciated. I've got access to an M1 machine myself, but it's not what I use day-to-day. We have a PR updating the build scripts for the profiler binaries at https://github.com/apache/netbeans/pull/6494 I think we have something for the terminal support somewhere too, although it might need a little work. In some ways, that's the easy part - we need a better way to handle releasing these for consumption in the main IDE build. The Windows launchers are currently in a separate repository, and released via Maven central - https://github.com/apache/netbeans-native-launchers We could use a similar approach. However, that might be more difficult for a cross-OS range of binaries (and with the profiler header generation)? We have a GitHub workflow file for building profiler binaries already at https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml That has the benefit of cross-OS building, including for macOS where we don't have an ASF Jenkins option currently. The workflow appears to be missing a source bundle that we could use for voting purposes, but could be adapted to generate that in an initial stage (we don't want the full NetBeans sources!). We could then look to release the binaries via dist.apache.org for consumption in IDE builds? Given there is not a huge amount of time before freeze for NB20, we could perhaps look to only update the binaries for macOS at this time, moving to ASF builds of the rest for NB21? Thoughts? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Wed, 4 Oct 2023, 20:07 Matthias Bläsing, wrote: > I was asked to reply here: > > I'm irritated, that votes are called for packages, that violate Apache > Release requirements (at least to my understanding). > > I will not vote on dlight.nativeexecution as I assume the reaction will > also be just a shrug. The question that remains: Why call a vote then? > So we can host the binaries on dist.a.o rather than the far worse shadow releasing via OSUOSL that was used for the last update. I'm sorry you're irritated by this, but understand it. I made a judgement call to keep the binary artefact contents the same for this first trial. This causes a minor violation of the release policy on convenience binaries, I realise, even though not really public facing. I wish I'd realised that earlier! It is still far less of one than putting them on OSUOSL in my opinion. It is at least a step in the right direction. The actual voting artefact (source) is compliant, if the contents are a little odd at present. Again, it was a judgement call to try this with the workflow without changing too much in the module itself. Both things need addressing in the NB21 cycle if this works for us. It's on my to-do list already leading on from this. If the vote doesn't pass then someone else will need to do the various PRs (I'm tied up most of next week), or we delay freeze, or we have another release without Apple Silicon support? I'm a little irritated with myself for not foreseeing this problem. Hindsight is great, sorry! Best wishes, Neil
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, I was asked to reply here: I'm irritated, that votes are called for packages, that violate Apache Release requirements (at least to my understanding). I will not vote on dlight.nativeexecution as I assume the reaction will also be just a shrug. The question that remains: Why call a vote then? Greetings Matthias Am Mittwoch, dem 27.09.2023 um 11:54 +0100 schrieb Neil C Smith: > Hi, > > The lack of native binaries supporting Apple Silicon (eg. profiler and > terminal) is becoming more and more of an issue, and costing us users. > I assume that is something we wish to address?! And incidentally, > while we're at it, if you're a NetBeans PMC member or committer using > it on macOS regularly on either Apple silicon or x86_64, your input > and testing through this would be very appreciated. I've got access > to an M1 machine myself, but it's not what I use day-to-day. > > We have a PR updating the build scripts for the profiler binaries at > https://github.com/apache/netbeans/pull/6494 I think we have > something for the terminal support somewhere too, although it might > need a little work. > > In some ways, that's the easy part - we need a better way to handle > releasing these for consumption in the main IDE build. > > The Windows launchers are currently in a separate repository, and > released via Maven central - > https://github.com/apache/netbeans-native-launchers We could use a > similar approach. However, that might be more difficult for a > cross-OS range of binaries (and with the profiler header generation)? > > We have a GitHub workflow file for building profiler binaries already > at > https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml > That has the benefit of cross-OS building, including for macOS where > we don't have an ASF Jenkins option currently. > > The workflow appears to be missing a source bundle that we could use > for voting purposes, but could be adapted to generate that in an > initial stage (we don't want the full NetBeans sources!). We could > then look to release the binaries via dist.apache.org for consumption > in IDE builds? > > Given there is not a huge amount of time before freeze for NB20, we > could perhaps look to only update the binaries for macOS at this time, > moving to ASF builds of the rest for NB21? > > Thoughts? > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, On Thu, 28 Sept 2023 at 12:19, Jean-Marc Borer wrote: > I am doing all my open source and home projects on macOS, which is the only > home computer brand I have (no Win in my home), but for the moment I don't > have yet a Silicon. If I can help, please let me know and Yes I definitely > wish that NB has a future on macOS ;-) Thanks! I've just posted a draft PR with the profiler binaries updated. https://github.com/apache/netbeans/pull/6502 There's a dev-build artefact available at https://github.com/apache/netbeans/actions/runs/6352543798 (you may have to scroll down to find it) I've tested I can now use the profiler OK on an M1 machine - be good to double check it's still working as before on an x86_64 macOS machine! :-) Ignore the failing Micronaut test - that's showing up in a bunch of places right now and isn't related. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
I am doing all my open source and home projects on macOS, which is the only home computer brand I have (no Win in my home), but for the moment I don't have yet a Silicon. If I can help, please let me know and Yes I definitely wish that NB has a future on macOS ;-) Cheers, JM On Wed, Sep 27, 2023 at 9:40 PM Neil C Smith wrote: > On Wed, 27 Sept 2023, 21:37 Michael Bien, wrote: > > > > Publishing binaries via Maven doesn't seem viable for this given > > > cross-OS build needed, so possibly looking at dist.a.o instead. > > (I assume you mean maven central the repo and not mvn the build system) > > Out of curiosity, why is it a problem? I used to put native libs into > > jars back when I wrote Java OpenCL bindings for example. > > > > I meant both. Take a look at the launchers repository. That particular > process seems difficult to split across multiple OS. Could be achieved in > other ways, sure, although still with more work. > > Best wishes, > > Neil >
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Wed, 27 Sept 2023, 21:37 Michael Bien, wrote: > > Publishing binaries via Maven doesn't seem viable for this given > > cross-OS build needed, so possibly looking at dist.a.o instead. > (I assume you mean maven central the repo and not mvn the build system) > Out of curiosity, why is it a problem? I used to put native libs into > jars back when I wrote Java OpenCL bindings for example. > I meant both. Take a look at the launchers repository. That particular process seems difficult to split across multiple OS. Could be achieved in other ways, sure, although still with more work. Best wishes, Neil
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, On 27.09.23 12:54, Neil C Smith wrote: The workflow appears to be missing a source bundle that we could use for voting purposes, ... Its a bit unfortunate that we have to set up releases for something what is only consumed by NB. I feel this project has enough to do during release already. However, since the main build doesn't produce those artifacts (and likely can't), we do have to version and upload them somewhere so that the main build can treat them as regular dependency and be somewhat reproducible. The libs look fairly stable to me so this probably doesn't have to happen often - so it might not add a lot overhead to the release process after all? Looking further I'm inclined to keep in this repo and adapt the GitHub workflow to include a source zip, and to release via dist.apache.org rather than Maven Sounds good to me. I slightly prefer dist.apache.org for internal artifacts which are only consumed by NB, maven central is also fine it just feels a bit wrong to use it for this. We should consider marking them as internal. Publishing binaries via Maven doesn't seem viable for this given cross-OS build needed, so possibly looking at dist.a.o instead. (I assume you mean maven central the repo and not mvn the build system) Out of curiosity, why is it a problem? I used to put native libs into jars back when I wrote Java OpenCL bindings for example. best regards, -mbien Thoughts? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Wed, 27 Sept 2023 at 13:35, Neil C Smith wrote: the generate headers section of each build - > I assume we could check the headers into a separate repo? But I don't > think we gain much by doing so, rather than adding a pre-build stage > on the existing workflow to build a source bundle. I've had a look at doing that in https://github.com/apache/netbeans/pull/6496 The artefacts are at https://github.com/apache/netbeans/actions/runs/6328665359 There's now a source bundle that is also consumed by the various native builds (prove it's all there!) What do you think? Probably needs some more work to be releasable? Right approach / wrong approach? Should also verify the native binary artefacts still actually work! :-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
I just recently received an M2 and it is not my everyday use machine yet. I can perform some testing using this device. Thanks, Josh Juneau On Wed, Sep 27, 2023 at 7:44 AM Neil C Smith wrote: > On Wed, 27 Sept 2023 at 12:41, Tamás Cservenák > wrote: > > Just my 5 cents: in Maven the mvnd project does deliver mac silicon > binary, > > and it works nicely. > > And the release binaries are built with GH workflow? Any concerns > raised / problems doing so? > > > Also, if needed, I can offer my M2 macMini for testing/developing (ie. > > shared via tailscale) if needed, as it is not my daily driver, mainly > just > > sits in a drawer. > > Thanks. I have an M1 machine locally (which also mostly sits in a > drawer! :-) ) but possibly others could benefit from it. > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Wed, 27 Sept 2023 at 12:41, Tamás Cservenák wrote: > Just my 5 cents: in Maven the mvnd project does deliver mac silicon binary, > and it works nicely. And the release binaries are built with GH workflow? Any concerns raised / problems doing so? > Also, if needed, I can offer my M2 macMini for testing/developing (ie. > shared via tailscale) if needed, as it is not my daily driver, mainly just > sits in a drawer. Thanks. I have an M1 machine locally (which also mostly sits in a drawer! :-) ) but possibly others could benefit from it. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
On Wed, 27 Sept 2023 at 12:33, Eric Barboni wrote: > But I thing we should tesselate the repo for thoose native stuff and make > release that we later use on netbeans main repo. > Maven was a choice to simplify release process but may not be compatible > with macos. I was in favour of a separate repo as well initially, but the workflow for the profile binaries means I've probably changed my mind. See the generate headers section of each build - https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml#L94 I assume we could check the headers into a separate repo? But I don't think we gain much by doing so, rather than adding a pre-build stage on the existing workflow to build a source bundle. > I cannot recall but I think some project use githubaction to make release > artefacts (sources + binaries) that are signed (this is per project/repo). So > maybe this could handle the issue. Yes, although signing is just for reproducible builds IIRC - trying to find something on this that isn't from the private members list. I assume this is the flow for mvnd releases? https://github.com/apache/maven-mvnd/blob/master/.github/workflows/release.yaml > Should we use nbpackage for macos/windows and make installer also "better" ? We already use nbpackage for macOS, and the Swift launcher is now built as part of that process. > Do we need to stick on release frame ? Or could we wait ? It would be better to hit the release if we can. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Just my 5 cents: in Maven the mvnd project does deliver mac silicon binary, and it works nicely. Also, if needed, I can offer my M2 macMini for testing/developing (ie. shared via tailscale) if needed, as it is not my daily driver, mainly just sits in a drawer. Thanks T On Wed, Sep 27, 2023 at 1:33 PM Eric Barboni wrote: > Hi, > I cannot use macos. Not having this kind of box. > > But I thing we should tesselate the repo for thoose native stuff and make > release that we later use on netbeans main repo. > Maven was a choice to simplify release process but may not be compatible > with macos. > I cannot recall but I think some project use githubaction to make release > artefacts (sources + binaries) that are signed (this is per project/repo). > So maybe this could handle the issue. > Launcher contains only windows but should contain mac/linux to be more > semanticaly correct to me. (Avoid special scenario) > > > Should we use nbpackage for macos/windows and make installer also "better" > ? > > Do we need to stick on release frame ? Or could we wait ? > > Best Regards > Eric > > On 2023/09/27 10:54:19 Neil C Smith wrote: > > Hi, > > > > The lack of native binaries supporting Apple Silicon (eg. profiler and > > terminal) is becoming more and more of an issue, and costing us users. > > I assume that is something we wish to address?! And incidentally, > > while we're at it, if you're a NetBeans PMC member or committer using > > it on macOS regularly on either Apple silicon or x86_64, your input > > and testing through this would be very appreciated. I've got access > > to an M1 machine myself, but it's not what I use day-to-day. > > > > We have a PR updating the build scripts for the profiler binaries at > > https://github.com/apache/netbeans/pull/6494 I think we have > > something for the terminal support somewhere too, although it might > > need a little work. > > > > In some ways, that's the easy part - we need a better way to handle > > releasing these for consumption in the main IDE build. > > > > The Windows launchers are currently in a separate repository, and > > released via Maven central - > > https://github.com/apache/netbeans-native-launchers We could use a > > similar approach. However, that might be more difficult for a > > cross-OS range of binaries (and with the profiler header generation)? > > > > We have a GitHub workflow file for building profiler binaries already > > at > https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml > > That has the benefit of cross-OS building, including for macOS where > > we don't have an ASF Jenkins option currently. > > > > The workflow appears to be missing a source bundle that we could use > > for voting purposes, but could be adapted to generate that in an > > initial stage (we don't want the full NetBeans sources!). We could > > then look to release the binaries via dist.apache.org for consumption > > in IDE builds? > > > > Given there is not a huge amount of time before freeze for NB20, we > > could perhaps look to only update the binaries for macOS at this time, > > moving to ASF builds of the rest for NB21? > > > > Thoughts? > > > > Best wishes, > > > > Neil > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: [DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, I cannot use macos. Not having this kind of box. But I thing we should tesselate the repo for thoose native stuff and make release that we later use on netbeans main repo. Maven was a choice to simplify release process but may not be compatible with macos. I cannot recall but I think some project use githubaction to make release artefacts (sources + binaries) that are signed (this is per project/repo). So maybe this could handle the issue. Launcher contains only windows but should contain mac/linux to be more semanticaly correct to me. (Avoid special scenario) Should we use nbpackage for macos/windows and make installer also "better" ? Do we need to stick on release frame ? Or could we wait ? Best Regards Eric On 2023/09/27 10:54:19 Neil C Smith wrote: > Hi, > > The lack of native binaries supporting Apple Silicon (eg. profiler and > terminal) is becoming more and more of an issue, and costing us users. > I assume that is something we wish to address?! And incidentally, > while we're at it, if you're a NetBeans PMC member or committer using > it on macOS regularly on either Apple silicon or x86_64, your input > and testing through this would be very appreciated. I've got access > to an M1 machine myself, but it's not what I use day-to-day. > > We have a PR updating the build scripts for the profiler binaries at > https://github.com/apache/netbeans/pull/6494 I think we have > something for the terminal support somewhere too, although it might > need a little work. > > In some ways, that's the easy part - we need a better way to handle > releasing these for consumption in the main IDE build. > > The Windows launchers are currently in a separate repository, and > released via Maven central - > https://github.com/apache/netbeans-native-launchers We could use a > similar approach. However, that might be more difficult for a > cross-OS range of binaries (and with the profiler header generation)? > > We have a GitHub workflow file for building profiler binaries already > at > https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml > That has the benefit of cross-OS building, including for macOS where > we don't have an ASF Jenkins option currently. > > The workflow appears to be missing a source bundle that we could use > for voting purposes, but could be adapted to generate that in an > initial stage (we don't want the full NetBeans sources!). We could > then look to release the binaries via dist.apache.org for consumption > in IDE builds? > > Given there is not a huge amount of time before freeze for NB20, we > could perhaps look to only update the binaries for macOS at this time, > moving to ASF builds of the rest for NB21? > > Thoughts? > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[DISCUSS] Native binary handling (or, does NetBeans have a future on macOS?)
Hi, The lack of native binaries supporting Apple Silicon (eg. profiler and terminal) is becoming more and more of an issue, and costing us users. I assume that is something we wish to address?! And incidentally, while we're at it, if you're a NetBeans PMC member or committer using it on macOS regularly on either Apple silicon or x86_64, your input and testing through this would be very appreciated. I've got access to an M1 machine myself, but it's not what I use day-to-day. We have a PR updating the build scripts for the profiler binaries at https://github.com/apache/netbeans/pull/6494 I think we have something for the terminal support somewhere too, although it might need a little work. In some ways, that's the easy part - we need a better way to handle releasing these for consumption in the main IDE build. The Windows launchers are currently in a separate repository, and released via Maven central - https://github.com/apache/netbeans-native-launchers We could use a similar approach. However, that might be more difficult for a cross-OS range of binaries (and with the profiler header generation)? We have a GitHub workflow file for building profiler binaries already at https://github.com/apache/netbeans/blob/master/.github/workflows/native-binary-build-lib.profiler.yml That has the benefit of cross-OS building, including for macOS where we don't have an ASF Jenkins option currently. The workflow appears to be missing a source bundle that we could use for voting purposes, but could be adapted to generate that in an initial stage (we don't want the full NetBeans sources!). We could then look to release the binaries via dist.apache.org for consumption in IDE builds? Given there is not a huge amount of time before freeze for NB20, we could perhaps look to only update the binaries for macOS at this time, moving to ASF builds of the rest for NB21? Thoughts? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
