- New Unmarshall script - hopefully the end of all compatibility issues, ever.
- GUI/CLI modes are now separate packages. In addition, the CLI mode now works.
- Release channels - before, beta versions had no update notifications. Now they do.
- Some hidden functionality that will be exposed in the near future.
- Major tidying up of the source code. Not much of a highlight for most, sure, but handy for me.
EDIT: I've had reports that Ruby 2.1 fails to work on 32-bit Windows XP. As Ruby 2.1 is more-or-less required for this version of RPGMaker Trans, that means I have to declare Windows XP unsupported. Anyone on WinXP? Please upgrade Windows. There's a lot of good reasons to do so.
Trying to use this on Linux. Things look different now. How do I do this?
ReplyDeleteHmm. Probably should right this up on the website. Or the new website when I make it. Anyhow, easiest way would be to grab the source and just run it. So for Ubuntu it'd be something along the lines of
Deletesudo apt-get install python3 python3-pip mercurial libqt4 libqt4-dev # Not sure on names of packages
hg clone https://bitbucket.org/habisain/rpgmakertrans
cd rpgmakertrans
sudo pip3 install -r requirements.txt
python3 -m cli OR python3 -m gui
(or run the rpgmakertrans_cli/rpgmakertrans_gui scripts with python3)
Note that all of these instructions are from memory and I'm tired now, so may not be 100% accurate. I'd also note that I'd set up a virtualenv rather than install packages onto the system python, but that's beyond the scope of my tired tutorial writing abilities.
Also... most modern RPGMaker games work great under Wine.
Oh, and to add to the list of things to install: ruby - RPGMaker Trans will quite happily use the system Ruby on Linux.
Delete(Gotta remember, this is still developed on Linux. In fact, performance running on Linux is somewhat better than Windows)
Note that "sudo pip3 install -r requirements.txt" might take a long time.
DeleteRecommended for user comfort: use the --verbose flag.
Installing PySide complained of a syntax error, but... it appears to have installed properly?
DeleteOkay, that didn't work right. Trying out virtualenv: http://docs.python-guide.org/en/latest/dev/virtualenvs/
DeleteHmm. Wasn't aware it was going to cause this much problems. So, two recommendations:
Delete1) Use virtualenv-wrapper . Little effort to set up, but very helpful (The setup command for a Python 3 virtualenv using virtualenv-wrapper is mkvirtualenv -p /usr/bin/python3 )
2) I noticed that there's now a python3-pyside package in ubuntu. If it's just pyside that's causing problems for your root install, try sudo pip uninstall pyside and then sudo apt-get install python3-pyside
Does this set of commands look right?
Deletevirtualenv -p /usr/bin/python3.4 venv
source venv/bin/activate
cd rpgmakertrans
pip3 --verbose install -r requirements.txt
python3 -m gui
Because it's giving an error:
ImportError: libpyside.cpython-34m.so.1.2: cannot open shared object file: No such file or directory
OK, so not entirely sure on this because I use virtualenv-wrapper, but virtualenv should have pip/python as the Python binary, not pip3/python3. That's pulling at straws... But maybe try with the 3 suffix? You may still be using the system install otherwise.
DeleteOther than that, the error indicates that PySide didn't run it's postinstall script. Not sure why that would be.
I'll try to get a set of instructions that works for me up when I'm on a proper internet connection.
As an aside, you may want to try the CLI version. That doesn't depend on PySide, so it should work even without it.
DeleteOK, I can verify that the following commands work (using virtualenvwrapper)
Deletemkvirtualenv -p /usr/bin/python3
pip install -r requirements.txt
This should produce no errors.
I'm a little puzzled on your need to explicitly link qmake. You may want to check the build dependencies of QT - maybe I've given the wrong packages.
That seems to have worked... once I dealt with Ubuntu 14.04's broken pyvenv-3.4
DeleteWhy on earth would they have pyvenv-3.4 as a package? Unless it's for testing the Python2 free Ubuntu... But I digress python virtual environments don't actually care about the host Python (i.e. installing the virtual environment packages for Python 2 let's you set up a Python 3 virtual environment)
DeleteRegardless, good you got it working in the end!
It's not a package. The problem is that the pyvenv-3.4 command is broken by somethingsomething with pip. Thus, you need to tell it not to install pip, then manually install pip in the virtualenv.
DeleteI found it kind of weird, annoying, obnoxious, you get the picture.
What I meant is that any command which is running Python virtualenv under a Python 3 host should be unnecessary. So just using the normal pyvenv command (as is used by virtualenv-wrapper) would work, and this wouldn't have the bugs.
DeleteProblem with non-obvious solution:
ReplyDeletesudo ln -s /usr/bin/qmake-qt4 /usr/bin/qmake
Wait, I meant to put this in that other comment thread
Delete