[ 
https://issues.apache.org/jira/browse/NETBEANS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daes Mond updated NETBEANS-2189:
--------------------------------
    Description: 
Problem using MinGW-TDM compiler

"No shell found. Cannot proceed. Please install either CYGWIN or Msys."

A work around is to choose MinGW (The 32-bit compatible version being use by 
netbeans previous versions), then rebuild the project, switch back to 
MinGW-TDM-64 bit and rebuild the project.  It will now work. Then when netbeans 
10 restarted back to same old routine to be able to use TDM.

[video of 
bug|http://topline2019.000webhostapp.com/nb10_mingw_tdm_bug_work_around_for_fix.mp4]

 

Finally I have found a way to create an alternate solution instead of just 
adding the path of MSYS or CYGWIN in windows PATH environment variable.  I have 
modified 
incubator-netbeans/ide/dlight.nativeexecution/src/org/netbeans/modules/nativeexecution/api/util/WindowsSupport.java
 to add a property file config for MSYS/CYGWIN. It's located at 
%USERPROFILE%\shell.properties (aka windows user.home).  Just add 
MSYS=/path/without/the/bin for MSYS

MSYS=C:\\msys2
usr

CYGWIN=C:\CYGWIN

 

Then I just modified the default message in Bundle.properties so it could 
notify howto use the alternate solution

 

Ultimately the best solution is to modify the C/C++ Developers Pack plugin so 
that user may have total control on how to configure the compilers and terminal 
emulators.  Like using different msys/mingw version and arch and diff cygwin 
version also.   As for my experience with just modifying PATH environment, it 
may have undesired side effects on the user normal use of computer. Also 
system("pause") will not work since msys/cygwin don't support it :P

 

  was:
Problem using MinGW-TDM compiler

"No shell found. Cannot proceed. Please install either CYGWIN or Msys."

A work around is to choose MinGW (The 32-bit compatible version being use by 
netbeans previous versions), then rebuild the project, switch back to 
MinGW-TDM-64 bit and rebuild the project.  It will now work. Then when netbeans 
10 restarted back to same old routine to be able to use TDM.

[video of 
bug|http://topline2019.000webhostapp.com/nb10_mingw_tdm_bug_work_around_for_fix.mp4]

 

Finally I have found a way to create an alternate solution instead of just 
adding the path of MSYS or CYGWIN in windows PATH environment variable.  I have 
modified 
incubator-netbeans/ide/dlight.nativeexecution/src/org/netbeans/modules/nativeexecution/api/util/WindowsSupport.java
 to add a property file config for MSYS/CYGWIN. It's located at 
%USERPROFILE%\shell.properties (aka windows user.home).  Just add 
MSYS=/path/without/the/bin for MSYS

MSYS=C:\\msys2\\usr

CYGWIN=C:\CYGWIN

 

Then I just modified the default message in Bundle.properties so it could 
notify howto use the alternate solution

 


> MinGW TDM Bug for fixing and temp workaround ("No shell found. Cannot 
> proceed. Please install either CYGWIN or Msys.")
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: NETBEANS-2189
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-2189
>             Project: NetBeans
>          Issue Type: Bug
>          Components: third-party - Other
>    Affects Versions: 10.0
>         Environment: Windows 10 Pro 64 bit with Msys/MinGW32 installed and 
> MinGW-TDM-64bit
>            Reporter: Daes Mond
>            Assignee: Daes Mond
>            Priority: Trivial
>         Attachments: Bundle.properties, WindowsSupport.java
>
>
> Problem using MinGW-TDM compiler
> "No shell found. Cannot proceed. Please install either CYGWIN or Msys."
> A work around is to choose MinGW (The 32-bit compatible version being use by 
> netbeans previous versions), then rebuild the project, switch back to 
> MinGW-TDM-64 bit and rebuild the project.  It will now work. Then when 
> netbeans 10 restarted back to same old routine to be able to use TDM.
> [video of 
> bug|http://topline2019.000webhostapp.com/nb10_mingw_tdm_bug_work_around_for_fix.mp4]
>  
> Finally I have found a way to create an alternate solution instead of just 
> adding the path of MSYS or CYGWIN in windows PATH environment variable.  I 
> have modified 
> incubator-netbeans/ide/dlight.nativeexecution/src/org/netbeans/modules/nativeexecution/api/util/WindowsSupport.java
>  to add a property file config for MSYS/CYGWIN. It's located at 
> %USERPROFILE%\shell.properties (aka windows user.home).  Just add 
> MSYS=/path/without/the/bin for MSYS
> MSYS=C:\\msys2
> usr
> CYGWIN=C:\CYGWIN
>  
> Then I just modified the default message in Bundle.properties so it could 
> notify howto use the alternate solution
>  
> Ultimately the best solution is to modify the C/C++ Developers Pack plugin so 
> that user may have total control on how to configure the compilers and 
> terminal emulators.  Like using different msys/mingw version and arch and 
> diff cygwin version also.   As for my experience with just modifying PATH 
> environment, it may have undesired side effects on the user normal use of 
> computer. Also system("pause") will not work since msys/cygwin don't support 
> it :P
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

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

Reply via email to