I am running NetBeans 8.0.2 on a 64-bit Windows 7 PC. I was trying to follow Geertjan Wielenga's instructions for getting up and running with Scala in NetBeans 8.x.
The first instruction starts, "In the Terminal window, ..." so I selected Window > IDE Tools > Terminal. Instead of being a useable terminal window, the tab's content area was completely gray. I noticed that there seemed to be text flashing in the window before it went gray, so I clicked on the "Create New Local Terminal Tab" button multiple times until I was able to read the disappearing text:
Unable to start pty process
Searching for this phrase yielded results for C/C++ projects and the "Run" command, but I'm not doing a C/C++ project. How can I get the terminal window to a state where I can interact with it?
The NetBeans Terminal Emulator requires Cygwin. Importantly, the bitness of NetBeans must match the bitness of Cygwin. If you are using a 64-bit version of NetBeans, then you must use a 64-bit version of Cygwin; likewise 32-bit and 32-bit.
This comment by Andrew Krazny on NetBeans bug 234221 says:
A bitness of jdk/netbeans is important. Possible options are:
32-bit NB and only 32-bit cygwin is installed
32-bit NB and only 64-bit cygwin is installed
32-bit NB and both 32/64-bit cygwin are installed
64-bit NB and only 32-cygwin is installed
64-bit NB and only 64-cygwin is installed
64-bit NB and both 32/64-bit cygwin are installed
Cases 1) and 5) are 'ideal' - in this case everything should work and it is highly recommended that bitness of NB/cygwin match. This means that if one tries to use cygwin64 (s)he should install 64-bit java and run 64-bit version of NetBeans (netbeans64.exe).
Case 2) is almost nonfunctional. It requires cygwin64/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 3) NB will detect 32-bit cygwin and will use it by default. IF user tries to add cygwin64 as a toolchain and compile his code in 64-mode, run in 'Output Window' will not work. 32-bit toolchain is OK in this case
Case 4) is almost nonfunctional. It requires cygwin/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 6) 64-bit compilation/run will work, 32-bit run will fail.
In my case, I was using 32-bit Cygwin with 64-bit NetBeans. I installed 64-bit Cygwin, added a CYGWIN_HOME environment variable, and added %CYGWIN_HOME%\bin to the end of my path¹, and now I have a functioning terminal window.
¹which I hate doing because there are command names that overlap
Related
I am trying to set up the debugger following a course in C language development. the option of the C++(GDB/LLDB) is not avaliable it is not showing in the command line pallet
vscode version 1.71.0
windows 10
cygwin64 installed
what am I missing to have that option for debugging.
I have minGW gcc installed on my computer from previous projects, and I have recently installed Msys2 so I could develop with GTK. Is it bad to have MinGW and a instance of MinGW on Msys2 installed on the same computer?
The only problem is that it might confuse you. It should not cause any real issues though, because MSYS2 does not add itself to your PATH environment variable, and when you run MSYS2 it will (by default) use a different PATH so you can only run Microsoft programs in C:\Windows and MSYS2 programs. So this means you won't accidentally run the compiler from one environment when you are in a different environment.
I'm writing a Kernel mode usb-driver primary for Windows Vista 32bit but hopefully it will also be able to be builded for Win XP, Win Vista, Win 7 32 and 64 bit.
Anyway, I'm debugging from an Windows 7 32bit laptop to a Windows Vista 32bit laptop (the target). The laptops are connected via Firewire and the connection seams to be ok since I can set some breakpoints and step trough parts of my code. All information is in assembly though and WinDbg says "Your debugger is not using the correct symbols..." when I hover over an function in my driver.
Symbol file path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Me\MyDriver\objchk_wlh_x86\i386
Source file path is:
C:\Me\MyDriver
Everything is newly compiled but WinDgb still won't accept my symbol files. Why?
If you can set breakpoints and step through your code it sounds like your symbols are fine. You can try:
!itoldyouso mydriver
If you want the debugger to convince you that your symbols are OK.
I never use the hover feature in the GUI, but it's entirely possible that it just doesn't work properly in some cases.
-scott
I have created an application in linux with GTK2 as GUI. It uses some linux-specific headers (e.g. arpa/inet.h) so to run under Windows I have to compile it with Cygwin. I downloaded the latest installer and choose to install GTK2 and its dependencies. My program compiled fine. But it needs X server to be running! I has old-style, ugly graphics and it doesn't open in a different window, like all Windows' applications do, but inside X server's window. Because of this it can't be portable. I found that guide, which is exactly what I need, but I get an error when I run "make" for GTK2 (undefined reference for _IID_IFilePersist, although I have uuid installed - also tried it with gtk2.20). Can you suggest what to do to build my application with cygwin? Or what do I need to install for the "_IID_IFilePersist" error? Thanks in advance!
There's prebuilt packages for windows that doesn't rely on X. http://gtk-win.sourceforge.net/home/index.php/Downloads
If you don't want X server to be running, then you're going to have to port the linux-specific parts of your code and compile with MinGW rather than Cygwin.
I just got this MSI wind netbook and tried to run eclipse on it. I installed JDK6 on the netbook already. Whenever I open eclipse there is nothing show up on the screen except a "warning sound" that alerts. What is the problem here?
ps.I just started learning java.
Most likely the Eclipse starter program can't find where you installed Java. Since Eclipse is a Java program, it needs a JRE installed (comes with the JDK typically) to run. Assuming you're running Windows on your MSI Wind, check to make sure the java executable is on your path in your computer environment settings (windows key + printscreen button, or windows key + pause button are the shortcuts to open the computer properties dialog if I remember correctly. Then go to advanced).
You can test if java is on the path by opening a cmd.exe shell window and typing 'java'. If it says it cannot find java, then you need to fix the path.
See this link for additional troubleshooting details: http://www.eclipsezone.com/eclipse/forums/t99010.html
You could try reinstalling the JDK. Perhaps having it on a different disk than the default (D: versus C:) is causing some trouble? It certainly isn't a problem with the hardware, I'm running Eclipse on Windows on an MSI Wind.
Use "Add/Remove programs" in the control panel to remove the java versions you have installed.
Then visit "java.com" and use it to install Java, and verify that it is working. You do not need more than that to use Eclipse.