What Is Microsoft Windows Nt 6.3 (9600)

[Latrina Mosely]

Iam trying to set VTK on windows (did I say it was complicated?^^).I have successfully configured VTK with CMake and I am now trying to run make through cygwin. However when I go to the build directory and enter make all the terminal prints and does is:

In English, that is "No targets specified and no makefile found." This tells you that GNU make is installed and running, but that you don't have a file called GNUmakefile, makefile, or Makefile in the current directory. It searches for those three, in order.

This is similar to the previous item: cmd.exe has no idea what to do with a POSIX path. Because Windows' file path parsing code sometimes treats forward slashes the same as backslashes, this gets interpreted as c:\usr\bin\make in this case, but there is almost certainly no c:\usr directory at all.

The reason this path works in the left screenshot is that Cygwin mounts your Cygwin installation directory (e.g. c:\cygwin or c:\cygwin64, by default) as the POSIX root, so that c:\cygwin\usr appears as /usr to any program linked to cygwin1.dll which uses POSIX APIs such as open(2). This includes Cygwin's version of GNU bash, as you show.

You should not require the explicit path within the Cygwin Terminal window, since /usr/bin should be ahead of anything else in the PATH. If that is not the case, you might not be using the Cygwin icon that setup.exe created, in which case you don't have a proper login shell. Either use that icon, or mimic what it does by calling mintty -, not just plain mintty.

I have been using Cura for quite a while and had no issues. Last night I opened six objects at once, multiple windows, and then Cura crashed. I tried to open it again and it would get past the splash screen then sit at a white screen with the hour glass.

OK. This is ridiculous. I created another new user profile and was using Cura. It was fine until I went to change the settings of a job. I changed it from Fine to VeryFine, then it locked up. The Cura log is saying the same thing. It's trying to connect to a com port (5) as in the log I posted above.

This might sound stupid, but this all started when I downloaded a 3D item from Cults3D. I tried to load that object in to Cura and the application crashed. It's almost like that item ruined my system.

The Cura team is trying to chase down a persistent slicing bug so you get me. Sorry. This is not my forte and I'm afraid to give misguided or plain old bad advice so I'll give no advice. I guess this is just a reassurance "somebody is paying attention" post.

This is often indicative of an issue with Cura running on some systems with multiple displays. Do you have multiple displays? If so, try keeping Cura on the primary display. But please let us know if you do indeed have multiple displays so we can diagnose what is going on.

Cura will crash on your system (not all systems with multiple displays) when it tries to open a window on the secondary display. This happens when you drag Cura to the secondary display and then open a window (Preferences, About, extensions, keep/discard profile settings, etc). It also happens on the next startup of Cura, when it tries to open the window directly on the secondary display. The latter can be mitigated by unchecking the option to "Restore window position on start" in the general preferences in Cura, but that does not fix the issue of opening dialog windows.

3a8082e126