Recent Posts

Pages: 1 2 3 4 5 6 7 8 9 10
1
Issues Help Desk / Re: Compile enigma on ClockworkPI GameShell
« Last post by Rebusmind on Today at 09:53:39 AM »
Wow, that's fantastic news! :D

Could you maybe write down the steps to compile an ENIGMA project directly on the GameShell? I'm planning to mostly test on Windows first and only as a last step compile and test on the GS, so I was hoping that I wouldn't need to set up a cross-compiling solution as well.

Once again thanks so much for taking the time to figure this out! :)
2
Issues Help Desk / Re: Compile enigma on ClockworkPI GameShell
« Last post by hpg678 on Today at 08:08:23 AM »
Greetings! I am so happy to announce that finally, I have been able to build ENIGMA and compile an empty game.  :dance: :dance:

Whew......that was indeed quite a challenge! At times it was frustrating, but in the end......totally worth it.  (Y) (Y)

I will be doing a video on it on my YouTube channel as well as an article on the procedure I did. In a nutshell, I had to


  • Update my Debian 9(Stretch) to Debian 10(Buster)
  • Download and Update Google Protobuf libraries
  • Install additional dependencies to cross-compile (although you don't have to if u want to)
  • modifying the Installation script for Linux Users in the WIKI


3
Issues Help Desk / Re: Compile enigma on ClockworkPI GameShell
« Last post by hpg678 on August 20, 2019, 06:31:22 AM »
Greetings!


Progress has been a bit disappointing when compiling ENIGMA. The errors i've encountered has to do with google protobuffers and libpugxml which are essential to building the compiler. The IDE LGM, loads up fine. I will continue to look into it.


I installed Raspbian Desktop onto a laptop and that is what i am using to test. The Laptop is a HP Pavillion dv6-321 with an AMD CPU, 6GB of DDR3 Ram and a 120GB SATA Hard drive. The OS is Debian 9. I've gotten Windows 32bit software to run, including Gamemaker 8 Pro and other games/projects compiled with ENIGMA.


So there you have it. Sorry its not good news but rest assured, I will continue to work on it.
4
Issues Help Desk / Re: Compile enigma on ClockworkPI GameShell
« Last post by Rebusmind on August 17, 2019, 02:42:33 PM »
As of the moment ENIGMA doesn't compile to ARM. I've been assured that 'it isn't that difficult to do' but time has me constrained for now. However, I do intend to look into it next week.
That's weird, the only reason I looked into ENIGMA was because someone in the GameShell forums told me it was able to combile to ARM. :D
Thanks for looking into the issue, I still feels very much lost. ^^'
5
Issues Help Desk / Re: Compile enigma on ClockworkPI GameShell
« Last post by hpg678 on August 16, 2019, 09:32:48 AM »
Greetings!


I've been able to install a Raspberry PI emulator on my Windows machine, but I've not been able to go any further yet.


I was thinking that if it is possible to have WINE or something similar to run Windows games, then it would be matter of compiling them as Windows .exe. As of the moment ENIGMA doesn't compile to ARM. I've been assured that 'it isn't that difficult to do' but time has me constrained for now. However, I do intend to look into it next week.



6
Issues Help Desk / Re: Incorrect display of g++ messages on Progress window
« Last post by hpg678 on August 16, 2019, 08:56:15 AM »
Greetings!


Unfortunately, I do get those as well.


There is a script at the root of 'enigma-dev' directory named "share_logs.sh" that will solve this........if you mind doing the extra work. As i understand it, you run the script in a terminal/shell window and it will strip those extra characters and create a pastebin file for you.


You can also use 'gdb' to debug your errors. Run the game in debug mode. Copy the name of resulting file....for example "/tmp/emg23453464548765342768.tmp" if you are running Linux;............. "C:/msys32/tmp/egm8652499151924152154.exe"...if you running Windows.
Open a Terminal window. (on windows open a Msys Shell Terminal, not a Powershell)
At the prompt, type gdb[ name of file you copied].
then type  'run'.


There you have it. You can use either of the two methods to debug your game. I personally have opted for the tedious method of looking through the output and figuring out where i made an error. This is only because i am meticulously saving the slightest change, so it is easier for me to know where i went wrong. :) :)


Hope this has 'helped' you out a bit. You can find on the discord channel. Or if you prefer, contact me here for anything else.


 (Y) (Y)

7
What i was trying to say is this is an obvious bug, and someone should report it if it hasn't been already. No, there is no way to 'turn it off', and no, it has no direct meaning. It needs to be fixed by one of the developers, most likely Josh. I only work on the engine, and don't know anything about how the compiler works. If it bothers you enough, make a GitHub ticket.
8
Issues Help Desk / Re: Incorrect display of g++ messages on Progress window
« Last post by tiborbuzasi on August 15, 2019, 02:48:03 PM »
Sorry, if the point of this issue was not clear: I'm asking why the output of g++ is littered if the characters (like ) in the g++ output have any special meaning or is there a known way to make them disappear to make the log more readable. This issue seems not to be related with my project as I tried to compile various source files from EDC and the g++ output appeared in the same style.

PS: added some more info to the first entry.
9
Yeah, normally it's a lot easier for me to debug errors like this with my own projects, simply because it's apparent enough what the exact code it is referencing is. I don't have access to your code, so it makes it that much more difficult for me to understand, I would recommend joining our discord and getting help from Josh there, or posting this as an issue on GitHub if there isn't already one posted for this.
10
Issues Help Desk / Incorrect display of g++ messages on Progress window
« Last post by tiborbuzasi on August 15, 2019, 01:58:22 AM »
I've been running into the same 'issue' both on Windows 7 x64 and Kubuntu 19.04 x64 (building enigma-dev from the source this morning and yesterday evening, respectively):
The error message of g++ is full of strange characters (see the attached image), which makes debugging even harder.

EDIT: providing some more info:
Pages: 1 2 3 4 5 6 7 8 9 10