You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@netbeans.apache.org by "pedro-w (via GitHub)" <gi...@apache.org> on 2023/03/09 10:48:05 UTC

[GitHub] [netbeans-native-installers] pedro-w commented on pull request #3: init build system for cleaner/launcher

pedro-w commented on PR #3:
URL: https://github.com/apache/netbeans-native-installers/pull/3#issuecomment-1461787752

   > I'm not sure to follow 100% but is it ok to merge. If we miss a 32bits/64bits target maybe we could iterate.
   > Would like to alter main repo to have a workflow to start integrate that.
   
   If I could chip in - I tried compiling as a 32-bit windows exe and AFAICS it was fine. I believe that a 32-bit parent can spawn a 64-bit child process and vice versa, so either type of stub would be able to start the JVM which runs NBI itself. However if the user were using 32-bit Windows then a 64-bit stub would not work for them. I know Windows 11 is 64-bit only but there are probably Windows 10 and earlier users with 32 bit installations. 
   Which is a round-about way of saying the stub should be 32-bit, unless there's another reason I've not understood!  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists