Guest deleted156886133 Posted March 10 Share Posted March 10 5 minutes ago, HeyYou said: Beyond my knowledge at this point. Everything I know about linux is written on the inside of my left eyelid..... Haha! Ok, fair enough. I suppose I'm on my own. Geez...Goddamn it! Â Link to comment Share on other sites More sharing options...
Guest deleted156886133 Posted March 10 Share Posted March 10 (edited) I went ahead and proceeded with the next part of step 10 of the tutorial, giving the commands make and make docs and it began compiling. Still too much terminal output even for a spoiler but I'll post the latter part below: Spoiler In file included from src/ui/widgets/lightingwidget.cpp:1: src/ui/widgets/lightingwidget.h:5:9: error: macro names must be identifiers   5 | #define <QAction>    |     ^ make: *** [Makefile:2226: GeneratedFiles/.obj/lightingwidget.o] Error 1 test -d /home/xxxxx/Build/nifskope/release/doc || mkdir -p /home/xxxxx/Build/nifskope/release/doc cd /home/xxxxx/Build/nifskope/build/docsys && python nifxml_doc.py && mv -f doc/*.html /home/xxxxx/Build/nifskope/release/doc && cp -f doc/*.* /home/xxxxx/Build/nifskope/release/doc && rm -f *.pyc /bin/sh: 1: python: not found make: *** [Makefile:1191: docs] Error 127 It seems the compiler found issues with the first file the tutorial says to modify, lightningwidget.h and a few other errors. Also, the release folder is still unpopulated. It simply has an empty folder called docs. No surprise there, I suppose. That's it for me for now. I'm going to ride my fixed gear. @HeyYou: Thanks for your time and consideration nonetheless. Edited March 11 by UsernameWithA9 Word deletion Link to comment Share on other sites More sharing options...
elvira0 Posted March 12 Share Posted March 12 I happened to come across this post while following the same tutorial, and I've managed to make it compile and run through some trial and error. What ended up working for me was ignoring the changes the guide makes in lightingwidget.h, and other than that just following the tutorial. I ended up having a missing library (libglu), but after installing that everything compiled fine and works as expected. Hope you can get it to work too. 1 Link to comment Share on other sites More sharing options...
Guest deleted156886133 Posted March 12 Share Posted March 12 No kidding? Well, I put that tutorial on the back burner and went searching for another way. I found this on Nifskope's github page through a DuckDuckGo search. Apparently, compiling with a piece of software called Qt Creator is possible on Ubuntu based OSs. The jury's still out on my end, however, as I'm in the process of downloading as I type. If it was successful, I was going to post the results here. So stand by, this could take a while. It's around 3.5GBs. Bloody hell. I must really love modding and playing Morrowind. Link to comment Share on other sites More sharing options...
AaronOfMpls Posted March 12 Share Posted March 12 16 minutes ago, elvira0 said: I happened to come across this post while following the same tutorial, and I've managed to make it compile and run through some trial and error. What ended up working for me was ignoring the changes the guide makes in lightingwidget.h, and other than that just following the tutorial. I ended up having a missing library (libglu), but after installing that everything compiled fine and works as expected. Hope you can get it to work too. Hmm, something I might keep in mind if I ever start modding with Nifskope. Link to comment Share on other sites More sharing options...
Guest deleted156886133 Posted March 12 Share Posted March 12 (edited) Ugh! This is becoming an exercise in futility. I just launched Qt Creator and was slapped in the face with the error dialogue below: Spoiler Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix the problem. Available platform plugins are: offscreen, vnc, minimalegl, linuxfb, wayland, vkkhrdisplay, eglfs, xcb, wayland-egl, minimal. 'Reinstalling the application may fix the problem.' Hah! I scoff at that statement because I downloaded/installed it late yesterday and was faced with the same dilemma. This morning, I uninstalled and tried again yet here I am. To be fair, it does say that it may fix the problem. However, that first line of the error dialogue is intriguing. If the plugin xcb was found, why didn't it load and initialize? Is it because it's listed in the message as an available plugin? That leads me to believe that it's not installed. Am I understanding the message correctly? I know. Head over to the software's respective support page, right? Then post an issue on another forum and wait for a reply. This rabbit hole is deeper and more complex than I thought. Perhaps I'll just throw my computer out the window. Before I go back to follow the advice of user @elvira0 , does anyone have any thoughts on Qt Creator? Maybe a preemptive solution thusly saving me a trip to Qt's website? I feel as if there is a simple solution but I don't see it due to my ignorance. While composing this post, I did a search for the plugin and found a handful of relevant hits. It seems as if this is not an isolated occurrence. Several users have posted a similar issue on a few different forums. In order to finally get Qt Creator running by installing the elusive xcb plugin, I ran the command below in the terminal... Courtesy of a user from the stackoverflow webpage. Spoiler sudo apt-get install "^libxcb.*" libx11-xcb-dev libglu1-mesa-dev libxrender-dev So, now, with a fresh new piece of software to become familiar with... Ugh!... I'll bid you folks adieu and attempt to puzzle this out. Edited March 12 by UsernameWithA9 Reworded a segment for clarification Link to comment Share on other sites More sharing options...
Guest deleted156886133 Posted March 12 Share Posted March 12 (edited) I entered into Qt Creator and instantly knew I was in trouble. Like a strange new land where nothing was familiar. Anyways, maybe I set up the new build project correctly, maybe I didn't. When I went to build, more errors. For fu<ks sake! Really? Let's just close Qt Creator for the moment before I put my fist through the monitor! Don't ask about the errors. Fortunately, they've been rendered irrelevant because I fell back on @elvira0 suggestion. I deleted the previous build files and performed a fresh git pull from Nifskope. Skipping the edit of the file lightningwidget.h, I restarted the tutorial at Step 6 until making a change at Step 10 because the command qmake-qt returns as an unknown command. I entered simply qmake and I was able to proceed with the next part. After entering the commands make and make docs in succession, it began to compile. There was one error: Spoiler make: *** [Makefile:1191: docs] Error 127 But there's a 99.999999% chance that that error is irrelevant because I now have Nifskope running natively on Linux! Be advised though, it's not actually installed as of yet. I launched it by right-clicking-->Open on the executable. I'll take that as a win. Maybe if I get fancy, I'll go back to the tutorial, continuing at Step 11 to perform the actual install but I'm good for now. To tell the truth, I have a few questions about Step 11 but will say no more here. Maybe @Foxroe, the tutorial's writer, can answer those inquiries. My new Nifskope on Linux: Thanks for reading folks. Today, I win. Edited March 13 by UsernameWithA9 I forgot something. Link to comment Share on other sites More sharing options...
Guest deleted156886133 Posted March 12 Share Posted March 12 Did I mention my brain hurts? Perhaps some THC will alleviate some of that. Link to comment Share on other sites More sharing options...
Foxroe Posted March 19 Share Posted March 19 Apologies to those of you that ran into trouble with the lightingwidget.h edit. I had you looking for and inserting "define" statements; however, those should have been "include" statements. I fixed the tutorial (thanks to @UsernameWithA9 ) Link to comment Share on other sites More sharing options...
Foxroe Posted March 19 Share Posted March 19 Also, with respect to "qmake-qt5", on my system (Slackware 15.0), it's just a symlink to "qmake". You can try just typing "qmake" instead, but you may need to find out if your *buntu distro uses a different symlink (if at all). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now