|
|
Post by AnthroHeart on May 18, 2021 5:30:03 GMT
I'm doing this on my Android. It's the only available option I have for now. Downloading the .cpp file goes smoothly, but compiling it is what gets the errors. I'm working on creating an Android Service that can be controlled using an Alexa Skill.
I'm not an android developer, but creating a service with no GUI, but only an Alexa VUI (Voice User Interface) might not be too hard.
|
|
|
|
Post by reden on May 18, 2021 5:35:50 GMT
Ok, I fixed a few bugs in the flag system, and some spelling mistakes:
Version 4.1
It's also formatted, the code, using clang-format to LLVM specs.
Here are the runtime examples for the 3 compiled versions. The Linux time function tells how long it takes to run. Remember it takes a bit to load it into memory.
I'm missing like wine-gecko or something that would give the terminal color when emulating windows.
You can manually change the terminal's background colour in File, Settings... it should be there. |
|
|
|
Post by AnthroHeart on May 18, 2021 5:36:56 GMT
No, when running WINE on my machine, and I say color RED, the text is still white.
|
|
|
|
Post by reden on May 18, 2021 5:37:00 GMT
Whatever do we need #include <bits/stdc++.h> for anyways if #include <iostream> works the same?
|
|
|
|
Post by AnthroHeart on May 18, 2021 5:39:27 GMT
It can probably be removed. I think I had it in there when I was trying to provide how much memory is free or something, but it got too difficult to do that. If you remove it, and it still compiles, then it isn't needed. I may do that in a future version if it works.
I just went by code examples, and pieced them together.
|
|
|
|
Post by reden on May 18, 2021 5:43:33 GMT
It can probably be removed. I think I had it in there when I was trying to provide how much memory is free or something, but it got too difficult to do that. If you remove it, and it still compiles, then it isn't needed. I may do that in a future version if it works.
I just went by code examples, and pieced them together.
Yes, it still compiles. That's what I had to do to compile it with Clang on Android, Mac and probably others. |
|
|
|
Post by AnthroHeart on May 18, 2021 5:46:45 GMT
Clang++ is just a little slower than g++, in the picture above,
14.5PHz vs 16.5PHz.
g++ is more performance, but clang++ is good for extensibility and larger projects.
|
|
|
|
Post by AnthroHeart on May 19, 2021 2:01:25 GMT
I am using a Raspberry Pi 3 as my desktop for now. I don't really need much performance. It has a desktop interface. It doesn't even have a fan, it uses such low power. So it's silent. It is a little slow at times, but I don't mind. This is the performance using 0.25 GB of RAM, on this. I can't really go much more than that, but even then I definitely feel it.  |
|
|
|
Post by AnthroHeart on May 19, 2021 2:02:13 GMT
Also, for Linux, the g++ compiler will give better performance than clang++.
It all comes down to your preference really.
|
|
|
|
Post by reden on May 19, 2021 2:13:46 GMT
I am using a Raspberry Pi 3 as my desktop for now. I don't really need much performance. It has a desktop interface. It doesn't even have a fan, it uses such low power. So it's silent. It is a little slow at times, but I don't mind. This is the performance using 0.25 GB of RAM, on this. I can't really go much more than that, but even then I definitely feel it. View AttachmentAre you using a Raspberry Pi (3) because you don't need much performance? I heard the 4 has pretty close to desktop-tier performance. |
|
|
|
Post by reden on May 19, 2021 2:15:50 GMT
Also I might note that SD Cards are not the most reliable storage medium. Try to have backups. SD Cards might die at unopportune times specially if they are constantly being battered with many writes and reads (they were invented for semi-sporadic reads).
|
|
|
|
Post by AnthroHeart on May 19, 2021 2:34:48 GMT
I am not doing many writes all the time. I have had the 3 for a bit now, and I can't afford to by a v4.
I have a 256GB flash drive plugged into it as my data drive as well.
|
|
|
|
Post by AnthroHeart on May 19, 2021 6:35:24 GMT
reden and taiI realized when holo-link is enabled, it's supposed to repeat HSUPLINK.TXT not INTENTIONS.TXT. So I updated this code to v4.2. But I am on my Raspberry Pi and can't seem to find a Windows compiler, or a MingW32 port for Rasperry Pi right now. My Ubuntu desktop completely crashed, so I can't use it and I don't feel like reformatting it at 1:30 AM. Can any of you compile this for Windows using preferably g++ as it's faster than clang++? I can't find the compiler flags that would include all libraries. It was posted somewhere on Sapien's forum I think. We need all the -- libraries included otherwise it won't work on another machine than where it is compiled. The compiler options were on my desktop that crashed. So I'm on my more stable Raspberry Pi. Changing INTENTIONS.TXT -> HSUPLINK.TXT when repeating should make a big difference. intention_repeater_max_4.2.cpp (37.12 KB)
|
|
|
|
Post by reden on May 19, 2021 15:03:23 GMT
There's also MinGW64 which can compile for 64 bits. 64 bits can use more than 4 GB RAM.
|
|
|
|
Post by AnthroHeart on May 19, 2021 15:14:07 GMT
My Raspberry Pi is only 32-bit.
I'm looking to reinstall Windows on my desktop. I have the license key for that.
But have to reset the CMOS jumper because it won't even show BIOS now. It goes into Ubuntu but then hangs.
|
|
