About Monkey 2 › Forums › Monkey 2 Development › Compiling on Ubuntu 14.04 LTS (fresh install)
This topic contains 36 replies, has 9 voices, and was last updated by
AdamStrange
1 year ago.
-
AuthorPosts
-
January 28, 2018 at 2:36 am #13301
^Your welcome
Thanks for posting your results as I’ll be putting this all into a guide soon.
January 28, 2018 at 5:23 am #13307libsdl2-dev
This apt-get makes things so much easier, thanks SDL!
February 8, 2018 at 12:29 pm #13567Just used DruggedBunny’s posted script on Ubuntu 17.10.
Worked like a charm – full download and build all in about 15 minutes.
Some notes:
- All bananas run extremely (unusably) fast. Literally hundreds of FPS. Is this just because the examples aren’t using any kind of delta timing, or is something messed up on my end?
- As others have pointed out, the monkey (Linux) executable name cannot be launched by double click as it wants to be opened as a shared library. Is this something that can be changed with compiler flags? Also, the naming convention is quite strange and awkward, especially with spaces and parenthesis..
- I’ve been anxiously following this project from the beginning as a long time BBasic and BMax user (and Blitz Plus, and Monkey 1..). I have been donating via Patreon since Mark made the option available, but not because I have used it at all – just because I think it’s an important project. So this is my first go with the language. Very very nice!
Thanks for the information guys, I’m excited to get things fully set up to test out other targets
February 8, 2018 at 2:37 pm #13568-Most bananas are using Vsync signal, so it’s supposed to run at your screen refresh rate (which is usually 60FPS). But some use a timer, I don’t remember which one though. You can search for the word Timer in the files and you’ll find them.
-I don’t think anybody has solved the non-launchable icon problem.
-nice indeed!February 9, 2018 at 2:35 am #13569I looked into the whole “shared library” executable problem.
The problem is not with Monkey, it’s with newer versions of GCC using the -pie option (PIE= Position Independent Executable, a newer security feature). Because of this, anything compiled with it will appear to Nautilus file manager as a shared library rather than an executable. I’ve read through tons of bug reports and complaints about the new behavior, and Nautilus devs don’t think it’s their job, the GCC devs don’t think it’s theirs, etc..
However, we can pass the -no-pie parameter to the linker to make “older style” executables. I did a quick test and it worked beautifully!
Monkey1234'LD optionsMX2_LD_OPTS_LINUX= -no-pieMX2_LD_OPTS_LINUX_DEBUG=MX2_LD_OPTS_LINUX_RELEASE=-s -O3I added -no-pie to the MX2_LDS_OPTS in bin/env_linux.txt than ran a rebuild2go
Now my executables launch as normal and even have the correct executable icon
February 9, 2018 at 5:08 pm #13576just filed a bug report for mark to consider this for Monkey2 default
April 19, 2018 at 7:16 am #14416Thanks to all the help I got on this.
I eventually gave up and started again – it works!!!!
Here’s what I did:
– Linux Mint 64bit Sylviasudo apt-get install g++ xorg-dev qtcreator libopenal-dev libgl1-mesa-dev libsdl2-dev
sudo apt-get install build-essential$ chmod +x scripts/*.sh
$ chmod +x bin/mx2cc_linux
$ cd scripts
$ ./rebuildall.shAfterwards there was a bin/ted2_linux/ted2 binary which enabled starting to code.
-
AuthorPosts
You must be logged in to reply to this topic.