Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
46
Issues Help Desk / Re: Enigma crashes on compile
« on: September 03, 2016, 07:16:18 am »
Try running make clean on your enigma directory.
47
Issues Help Desk / Re: Enigma crashes on compile
« on: August 31, 2016, 10:16:54 am »
Ok, I've filed a bug report here: https://github.com/enigma-dev/enigma-dev/issues/1006
48
Developing ENIGMA / Re: SDL2 Support?
« on: August 31, 2016, 06:33:35 am »
There's no one working on SDL2 support, right now the main focus is on finishing off the last bits of OpenGL3 support. SDL2 support would be great though, I would be really appreciative and I think the other guys would be more than happy for someone to implement SDL2.
49
Issues Help Desk / Re: Error downloading the examples from this page
« on: August 31, 2016, 06:26:43 am »
Nah, the links aren't broken, someone's probably just forgotten to update the SSL cert or something. For now you'll have to whitelist enigma-dev.org in your browser, until Robert or Josh or someone else stops adulting for a bit and checks up here.
50
Issues Help Desk / Re: Enigma crashes on compile
« on: August 31, 2016, 06:17:45 am »
Wait a second, what version of GCC and G++ are you using? I'm asking since I see:
Code: [Select]
ERROR(/usr/include/c++/5//bits/c++0x_warning.h,34,54): #error This file requires compiler and library support \
for the ISO C++ 2011 standard. This support must be enabled \
with the -std=c++11 or -std=gnu++11 compiler options.
51
Issues Help Desk / Re: Enigma crashes on compile
« on: August 30, 2016, 04:21:40 am »
This is a bug with OpenJDK, not ENIGMA. Try updating OpenJDK, if that doesn't fix it try using Oracle's Java. Please tell me if either fix the issue.
I can tell because of this:
I can tell because of this:
Code: [Select]
*** Error in `java': free(): invalid pointer: 0x82cc1fd0 ***
*** Error in `java': corrupted double-linked list: 0x82cc1f50 ***
Since Java has garbage collection it must be an issue caused by the runtime,.
52
Issues Help Desk / Re: Enigma crashes on compile
« on: August 26, 2016, 01:58:33 pm »
Can you post the full log please?
53
Issues Help Desk / Re: Enigma crashes on compile
« on: August 26, 2016, 03:04:24 am »
Install it with this script:
Code: [Select]
#!/bin/bash
cd
echo "Installing dependencies..."
sudo apt-get install g++ zlib1g-dev libglu1-mesa-dev libalure-dev libvorbisfile3 libvorbis-dev libdumb1-dev git default-jre wget
echo "Downloading Enigma..."
git clone git://github.com/enigma-dev/enigma-dev.git
cd enigma-dev
echo "Downloading easy startup script..."
wget http://pastebin.com/raw/6ZmrzWKP -O start.sh
sed -i -e 's/\r$//' start.sh
echo "Correcting permissions..."
chmod +x start.sh
chmod +x install.py
echo "Installing..."
./install.py
cd CompilerSource
echo "Rebuilding compiler..."
make clean
make
echo "Done, to start Enigma just run ~/enigma-dev/start.sh"
54
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 31, 2016, 05:03:36 am »
No, make a pull request, your changes are important and useful and that way you'll get listed as a contributor, ENIGMA for OSX is seriously undertested and I think it hasn't been worked on for 2 years, don't be shy and well done 
56
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 29, 2016, 03:57:18 am »
Found the code that sets the make directory:
https://github.com/enigma-dev/enigma-dev/blob/03b754e1907fb840e4b745252333e504151bae7c/CompilerSource/settings-parse/parse_ide_settings.cpp#L150
My equivalent of that folder is ~/.enigma which looks like:
So the real issue here is that the Preprocessor_Environment_Editable isn't being created, or is maybe being created in the wrong place.
Can you post your whole compile log?
https://github.com/enigma-dev/enigma-dev/blob/03b754e1907fb840e4b745252333e504151bae7c/CompilerSource/settings-parse/parse_ide_settings.cpp#L150
My equivalent of that folder is ~/.enigma which looks like:
So the real issue here is that the Preprocessor_Environment_Editable isn't being created, or is maybe being created in the wrong place.
Can you post your whole compile log?
57
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 28, 2016, 05:05:51 pm »
I'm guessing that because enigma-dev's .gitignore ignores ./ENIGMAsystem/SHELL/API_Switchboard.h that SHELL is indeed where it's supposed to be placed. We need to figure out what exactly is generating that file, since it seems to be autogenerated.
Edit: The file is created right here, it get's the path from 'makedir'
https://github.com/enigma-dev/enigma-dev/blob/03b754e1907fb840e4b745252333e504151bae7c/CompilerSource/settings-parse/parse_ide_settings.cpp#L76
Edit: The file is created right here, it get's the path from 'makedir'
https://github.com/enigma-dev/enigma-dev/blob/03b754e1907fb840e4b745252333e504151bae7c/CompilerSource/settings-parse/parse_ide_settings.cpp#L76
58
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 28, 2016, 04:00:03 am »
I don't get that folder on Linux so I have no idea what you're talking about. What files does ./ENIGMA have in it? Try adding -I./ENIGMA to searchdirs.
59
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 27, 2016, 04:45:36 am »
What do you mean by './ENIGMA'? I can't find a folder by that name.
Either way try changing:
searchdirs: gcc -E -x c++ -v $blank -I./ENIGMAsystem/SHELL/
to
searchdirs: gcc -E -x c++ -v $blank -I./ENIGMAsystem/
Either way try changing:
searchdirs: gcc -E -x c++ -v $blank -I./ENIGMAsystem/SHELL/
to
searchdirs: gcc -E -x c++ -v $blank -I./ENIGMAsystem/
60
General ENIGMA / Re: Learning to Develop ENIGMA
« on: July 26, 2016, 04:29:25 am »
Try changing these in gcc.ey:
resources: ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode.res
Run-output: ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode
Run-Program: open ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode
to:
resources: ./EnigmaXcode.res
Run-output: ./EnigmaXcode
Run-Program:./EnigmaXcode
If that doesn't work try different variations, like just changing resources or leaving just one the same.
resources: ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode.res
Run-output: ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode
Run-Program: open ./MacOS/build/Release/EnigmaXcode.app/Contents/MacOS/EnigmaXcode
to:
resources: ./EnigmaXcode.res
Run-output: ./EnigmaXcode
Run-Program:./EnigmaXcode
If that doesn't work try different variations, like just changing resources or leaving just one the same.