We’ve been trying to get SikuliX 2.0.5 to run on a RHEL 8 system, and not having much luck.
We went through the instructions on this webpage:
https://sikulix-2014.readthedocs.io/en/latest/newslinux.html#newslinux
We started on RHEL 7, but the OpenCV shared library required a newer version of GLIBC than is standard on RHEL 7 (version ‘GLIBC_2.27’ not found (required by ~/.Sikulix/SikuliLibs/libopencv_java430.so)), so we moved up to RHEL 8. We had to build OpenCV (v4.3.0) from source because we could not find a java companion package for RHEL 8, which required quite a few other dependencies, but in the end we got it built with most options enabled, and installed as root on the system. We also got Tesseract installed via a package, as well as xdotool and wmctrl.
We are setting LD_LIBRARY_PATH to ensure that the OpenCV libs are picked up, and when we run with the “-v -c” options to the IDE, there are no obvious problems reported. It seems to believe it is moving the mouse, though we can see that it is not, and when we try to capture a screenshot, the “canvas” from which to capture is either uninitialized/garbage frame buffer memory, or a totally black screen. On rare occasions we have seen the actual desktop, but most times we do not.
Originally the system had 2 monitors, but was subsequently reconfigured to a single display system. We were originally running remotely over NoMachine, but have also tried running locally and observed no difference in behavior.
Any pointers or suggestions would be most welcome. Given that no error messages are being reported, we are out of ideas for how to proceed in debugging the problem. It appears that more native support is provided for Debian-based systems, but we’re attempting to validate a product which only advertises support for RHEL systems, so we’d prefer to get it working in this environment if at all possible.
Our agency requires that all Windows software be packaged by a central group. We've been using STS on Windows 7 for quite a while. I can't find any kind of official statement to indicate that it will run on Windows 10. Is STS working for folks running Windows 10 64 bit (HP hardware, if that makes a difference).
Several of us have tried finding information on the STS official site and I have submitted an issue to the STS issue tracker but it is unassigned. It would be helpful if we could point to some practical experience or success with this.
Thanks in advance,
Leila
I received a very helpful comment from Martin Lippert on the STS issue tracker site. He said "The latest version of STS (3.8.3) as well as the upcoming version (3.8.4) are based on Eclipse Neon, which has Windows 10 as a supported target environment defined (https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml). Therefore you can run STS on Windows 10."
We also tested it on a test computer and it seems to be working fine.
I'm using Ubuntu 14.04 (64 bit). After installing leJOS_NXJ_0.9.1beta-3, I was able to flash the NXT device. However, when I tried to upload a program, it showed a message "Found NXT: NXT 0016530CDF15" and then just stuck there.
I also tried Eclipse with leJOS plugin, and got the same problem. It showed
Program has been linked successfully
Uploading ...
Found NXT: NXT 0016530CDF15
and it got stucked there.
Can anybody help me with this issue?
Thanks,
Thuy
This site might be able to help, it provides the information to install and configure correctly all the software necessary for you to develop Java programs for the NXT, maybe by following this site it will hopefully fix the problem.
This tutorial will show you how to install and configure all the software necessary for you to develop Java programs for the LEGO Mindstorms NXT. Java is much more powerful and flexible than the original NXT-G software that LEGO provides. We will be using the Eclipse editor to write the actual Java code and to download this into the NXT. This combination enables you to conveniently write software and to quickly test it on the NXT. Of course there are many other Java editors, but we consider this combination to be particularly convenient. This tutorial focuses on the Windows XP platform, A Mac OS X tutorial is also available. We have two additional steps for Windows Vista. You will work through the following five steps - See more at: http://www.bartneck.de/2008/03/04/java-lego-nxt-eclipse-tutorial/#sthash.h1ZOZvlX.dpuf
I was looking for a debugger for Windows, other than GDB, which is freely accessible. I found WinDbg and it looks quite good so I wanted to give it a try. Now when I go to the MSDN page it offers to download the SDK for Windows 8. As this is a rather big package, I wonder if I can use this WinDbg version still for Windows XP?
Since my company still uses Windows XP for some time to come, I'm stuck with it for now. Is there another, free debugger which is user friendly?
I'm used to Visual Studio for debugging, which is quite nice. Currently I use Eclipse with GCC and GDB. GDB is good enough, but when I do some assembly I don't really like it, and all in all I don't find it very user friendly.
The latest WinDbg will work with Windows 2000 onwards and most commands work with Windows XP. There will be some that will only work with later versions, but these are documented in the included help file.
Just to ease your download pain, firstly there is the option to select what to download from MSDN, or you can just download the version you want here thanks to a kind person who is hosting the individual components.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Does anyone know how to get ahold of windbg without having to download the entire 620MB WDK ISO?
All I can find on the net to download the debugger is this link, which says you have to get the whole WDK: http://www.microsoft.com/whdc/devtools/debugging/default.mspx.
Actually, Microsoft has now made the Debugging Tools downloadable separately from the SDK. Look for the section "Standalone Debugging Tools for Windows (WinDbg)" about mid-page:
for Windows 8.1
for Windows 10
Officially, you can't. But someone's been extracting them for your convenience and hosting them.
Note: You can get the older releases on the official site, but the latest ones are part of the WDK.
If you run winsdk_web.exe from the following link, you can selectively install windbg or extract windbg installer msi.
Microsoft Windows SDK for Windows 7 and .NET Framework 4
http://go.microsoft.com/fwlink/?LinkID=191420
The standalone MSI file of windbg can be downloaded from here. The version is 6.12.0002.633 (x86). http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi
If you're on Windows 7 x64, the solution provided by Sukesh doesn't work.
I managed to install the debugging tools by downloading the Windows SDK installer for Windows 8 (here), and then choosing "Debugging Tools for Windows" in the installer:
http://codemachine.com/downloads.html
Has all the individual msi files
Try the MSDN archive link at http://archive.msdn.microsoft.com/debugtoolswindows/Release/ProjectReleases.aspx?ReleaseId=4912. It has the WinDbg MSI for both 32- and 64-bit (Version 6.12.2.633).
I found both, x64 and x86 version 6.12.0002.633 here:
http://rxwen.blogspot.de/2010/04/standalone-windbg-v6120002633.html
The saga continues with the Windows 10 version. I had to install Win Debug Tools on clean Windows 10 OS with Visual Studio 2015.
To make a long story short, just follow the instructions in the link provided by David Black. After downloading the files, instead of running the SDK installer, browse to the installers directory and execute the msi files directly.
I wonder how many man hours have been lost through the last decade because of MS sloppiness in regards to WDK/SDK installation?
You can also get it from Chocolatey:
https://chocolatey.org/packages/windbg
For Windows 7 x86 you can also download the ISO:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8442
And run \Setup\WinSDKDebuggingTools\dbg_x86.msi
WinDbg.exe will then be installed (default location) to:
C:\Program Files (x86)\Debugging Tools for Windows (x86)
I was looking for the same thing for a quick operation and found this question. I needed both 32-bit and 64-bit versions.
This is an older version but the links are from the Microsoft servers, it should be safe. The link for 32-bit version is also in a previous answer but the version number i get on the install is different, maybe the same link is updated with a newer version since 2013.
Cheksums are generated both locally and on VirusTotal, they match.
Debugging Tools for Windows (x64) (6.12.2.633)(VirusTotal Scan): http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_amd64/dbg_amd64.msi (SHA-256:2e491bb98850abf9b9d2627185b57e048ba9b2410d68303698ac68c2daad9e5d)
Debugging Tools for Windows (x86) (6.12.2.633)(VirusTotal Scan): http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi (SHA-256:5a0f43281e51405408a043e2f94dd51782ef29671307d3538cfdff5b0e69d115)
I tested the 64 bit debugger with a 64 bit program that was compiled some years ago (~2012) and it works. Test is done on Windows 10 Pro 64 bit (v2004 Build 19041.207).
WinDbg is now available separately via MS Store. It's called "Preview" but I tested it to analyse some memory dumps and it works fine.
If you're on Windows 10 - launch MS Store, type "WinDbg" in the search box and voi-la - you have it. The download is approx. 100mb. It will downlaod required symbols automatically.
This Microsoft link allows you to select the SDK. When you run the install and only select Windows debugging tools it will only download 288mb and install the tool as stand alone.
https://developer.microsoft.com/en-us/windows/hardware/download-windbg