AROS World Exec
Development => AROS Software Development => Topic started by: miker1264 on March 04, 2023, 11:29:44 AM
-
My testing environment is just about ready for x86-64 for ABIv11 software & system files.
I'm still working on the icons & I have to Refresh my ABIv11 Build System to add software to test.
-
My testing environment is just about ready for x86-64 for ABIv11 software & system files.
I'm still working on the icons & I have to Refresh my ABIv11 Build System to add software to test.
Up!
-
Miker I fixed the iso of Tiny Aros so that you can use it in VM :)
https://drive.google.com/file/d/1f6Z3ls5VSEu50KCLL039noi5nZhI5blB/view?usp=sharing
-
Miker I fixed the iso of Tiny Aros so that you can use it in VM :)
https://drive.google.com/file/d/1f6Z3ls5VSEu50KCLL039noi5nZhI5blB/view?usp=sharing
@Amiwell
Thank you. I will download it and give it a try. :)
The benefit to me of distributions like TinyAros is that they have a very small download size.
Especially since I have multiple build systems in VMWare & multiple test systems in VirtualBox then of course distro size is important.
I have a 1TB SSD as my primary drive on my programming laptop. The drive is nearly full of mostly AROS or Amiga related data. I need to install the new 2TB SSD I bought.
Thanks again,
Mike R.
-
We must realize that AROS is NOT Amiga. Although they both have some similar features and structure and of course many Amiga programs run on AROS 68k they are not the same. I like to say "AROS has one foot in the past with an eye towards the future". We have Classic and Modern ways of accomplishing the same tasks.
In that sense we have to look to the future to help improve AROS. It can be so much more than just a hobby OS. We have the horsepower with modern CPU's and super fast Memory as well as the potential of Powerful Graphics. Combined with the Speed of Solid State Drives there's no theoretical reason why AROS can't be fast and efficient.
Much of what AROS lacks has to do with software and applications. I'm not just talking about Office Apps, Email Clients and Web Browsers. Many applications that we use had their start on 30-year old computer systems. Classic Amiga Software seems antiquated and lacking in places.
Other than lacking and the underlying infrastructure there's no reason AROS can't enjoy having fast Web Browsers. We just don't have them. There are many Modern features that seem to be missing. I will just mention a few of them.
Rather than having a handmade or cartoonish look AROS should have colorful high quality icons and window themes. The eye candy attracts new users. Although we have Icon Tooltypes and Datatype Descriptors why don't we have cohesive system-wide file associations. Each file could have it's own descriptor that identifies it and the system "knows" what the default tool is that is associated with it . Another component is a working Package Manager.That would include tracking installed library versions. We have some of that but it could be much more useful.
Workspace that IcarosDesktop was using is a great idea to keep important user files in a central location. The "Extras" drawer has also become a good add-on location for miscellaneous user files and useful programs.
Although AROS has roots in the Amiga world of the past we shouldn't be afraid to innovate. The Classic and Modern features can co-exist to make AROS in all it's flavors better for everyone.
-
Especially since I have multiple build systems in VMWare & multiple test systems in VirtualBox then of course distro size is important.
This is true, but if you have to have the complete Development package (600 MB or so), the Operating System and a few system applications, plus space for program installations to test, here you need at least a 2GB Hardisk.
Saving on AROS which is our system of choice I don't find fair, my AROS One x86 complete with almost all the most common existing Applications for AROS, including many games is only 3GB.
Much of what AROS lacks has to do with software and applications. I'm not just talking about Office Apps, Email Clients and Web Browsers. Many applications that we use had their start on 30-year old computer systems. Classic Amiga Software seems antiquated and lacking in places.
I agree, native programs are needed on AROS that can develop compatible data on other platforms as well, AMiGA softtware belongs to the past and nostalgic people who do not care about the future and priogresses on AROS.
Rather than having a handmade or cartoonish look AROS should have colorful high quality icons and window themes. The eye candy attracts new users. Although we have Icon Tooltypes and Datatype Descriptors why don't we have cohesive system-wide file associations. Each file could have it's own descriptor that identifies it and the system "knows" what the default tool is that is associated with it . Another component is a working Package Manager.That would include tracking installed library versions. We have some of that but it could be much more useful.
Correct, that's what I set out to do when I started ola my Distro, create an old style Distro, with different sized icons and old style, or have ugly windows with lots of graphic artifacts, for those approaching AROS it will only be able to make tenderness and then the whole thing will be trashed
-
Miker I fixed the iso of Tiny Aros so that you can use it in VM :)
https://drive.google.com/file/d/1f6Z3ls5VSEu50KCLL039noi5nZhI5blB/view?usp=sharing
@Amiwell
Thank you. I will download it and give it a try. :)
The benefit to me of distributions like TinyAros is that they have a very small download size.
Especially since I have multiple build systems in VMWare & multiple test systems in VirtualBox then of course distro size is important.
I have a 1TB SSD as my primary drive on my programming laptop. The drive is nearly full of mostly AROS or Amiga related data. I need to install the new 2TB SSD I bought.
Thanks again,
Mike R.
Thank you Miker
-
We must realize that AROS is NOT Amiga. Although they both have some similar features and structure and of course many Amiga programs run on AROS 68k they are not the same. I like to say "AROS has one foot in the past with an eye towards the future". We have Classic and Modern ways of accomplishing the same tasks.
In that sense we have to look to the future to help improve AROS. It can be so much more than just a hobby OS. We have the horsepower with modern CPU's and super fast Memory as well as the potential of Powerful Graphics. Combined with the Speed of Solid State Drives there's no theoretical reason why AROS can't be fast and efficient.
Much of what AROS lacks has to do with software and applications. I'm not just talking about Office Apps, Email Clients and Web Browsers. Many applications that we use had their start on 30-year old computer systems. Classic Amiga Software seems antiquated and lacking in places.
Other than lacking and the underlying infrastructure there's no reason AROS can't enjoy having fast Web Browsers. We just don't have them. There are many Modern features that seem to be missing.
First you need modern development tools (compilers, libraries, IDEs), to better support developers.
Only after that you can think about adding modern features.
-
AMIGASYSTEM & Amiwell & everyone else who maintain AROS Distros you're doing an amazing job to help AROS.
For me large distros of 3.5GB are not practical. Just like IcarosDesktop has a full version & a lite version, at times the lite version is better. I only have 5GB of space left on my primary drive.
I sometimes use IcarosDesktop x86 for testing. Originally I had AROS Hosted on Windows. Then I switched to AROS Hosted on Ubuntu Linux. But therein is the problem. I can't do much testing because Magellan, for whatever reason, is highly unstable in Hosted Mode. So instead I have AROS One x86 installed Native Mode in VirtualBox. By comparison saving the virtual machine for Ubuntu takes 1 or 2 minutes which seems like a long time. AROS One x86 takes only 5 seconds to completely shut down. Start up is quick too.
I also have a newer version of AROS One x86 installed natively on my Mini PC that uses an Intel Atom CPU. To my great surprise every peripheral device, USB floppy, CD-ROM, Zip Drives, it all just works! That's a good user experience.
AROS Vanilla is not a full distro. It is a recent Nightly Build or more recent package release of core system file will high quality icons, colorful window themes and an extras add-on. It has an Extras drawer with a small selection of software. It also has a Workspace to store documents, pictures, music.
Agreed. Having good programming tools including IDE's is necessary for development. Murks is a good idea. Gcc in the shell is also good. I also use AmiDevCPP as an IDE.
-
Then I think that a distro only for developers / testing would be a Good Thing to have.
Something which is slimmer than AROS One x86, but with all relevant tools needed for developers.
Regarding the "desktop manager", Wanderer is very simple but also very limited. Magellan / Directory Opus is the opposite: a monster (of complexity as well). Maybe Scalos could fit in the middle.
-
. I can't do much testing because Magellan, for whatever reason, is highly unstable in Hosted Mode. So instead I have AROS One x86 installed Native Mode in VirtualBox. By comparison saving the virtual machine for Ubuntu takes 1 or 2 minutes which seems like a long time. AROS One x86 takes only 5 seconds to completely shut down. Start up is quick too.
I also have a newer version of AROS One x86 installed natively on my Mini PC that uses an Intel Atom CPU. To my great surprise every peripheral device, USB floppy, CD-ROM, Zip Drives, it all just works! That's a good user experience.
Meanwhile thank you for preferring AROS One on your PCs, I recommend to use it on VM as well, in fact the systemsLinux on VM are very slow to boot, ditto to exit.
AROS on the other hand is very fast, in a few seconds you aviate and close the operating system, Ditto for AROS 68k, with WinUAE AROS 68k boots in very few seconds. closing is immediate.
All of this speeds up a lot of testing that on hosted Linux to do the same thing (dozens of reboots) would take you a day.
AROS One was created to facilitate this, every file is recognized by the system, and this saves you a lot of time in file testing.
Now I am doing a little modification for text files, unfortunately no Text Editor on AROS allows dragging and dropping files, except for "NoWinED", too bad that on first startup the no,i of the keys get obscured, on solves it just by enlarging the GUI.
To have more speed, now I decided that each text file, once clicked opens directly with "Editor", very convenient to edit startup, config file etc..
-
@cdimauro
I would say that Magellan is just a Monster and that's it, both on OS3 and AROS, Magelln "which I know well" has always been a foreign body on Amiga, ditto on AROS, the user gets lost in the meanders, nothing is "Amigoso", in fact very few people use it.
Wander which then is nothing more than a Workbench, is so easy and intuitable that even a child can use it, it is not true that it cannot give what Magellan offers, at some junctures it is even better organized, see the many system preferences.
Magellan like Ambient on MOS (its descendant) has its Prefs on one GUI, this means that one problem involves the other preferences as well.
If you have never used AROS One, I suggest you try it, then maybe you will appreciate Wanderer more.
--- Italiano ----
Direi che Magellan è solo un Mostro e basta, sia su OS3 che AROS, Magelln "che conosco bene" è sempre stato un corpo estraneo su Amiga, idem su AROS, l'utente si perde nei meandri, nulla è "Amigoso", infatti sono veramente in pochi ad utilizzarlo.
Wander che poi altro non è che un Workbench, è talmente facile e intuibile che anche un bambino può utilizzarlo, è non è vero che non può dare quello che offre Magellan, in alcuni frangenti è pure meglio organizzato, vedi le tante preferenze del sistema.
Magellan come Ambient su MOS (suo discendente) ha le sue Prefs su una sola GUI, questo significa che un solo problema coinvolge anche le altre preferenze.
Se non lo hai mai usato AROS One, ti consiglio di provarlo, poi magari apprezzerai di più Wanderer.
-
@cdimauro
I would say that Magellan is just a Monster and that's it, both on OS3 and AROS, Magelln "which I know well" has always been a foreign body on Amiga, ditto on AROS, the user gets lost in the meanders, nothing is "Amigoso", in fact very few people use it.
Wander which then is nothing more than a Workbench, is so easy and intuitable that even a child can use it, it is not true that it cannot give what Magellan offers, at some junctures it is even better organized, see the many system preferences.
Magellan like Ambient on MOS (its descendant) has its Prefs on one GUI, this means that one problem involves the other preferences as well.
If you have never used AROS One, I suggest you try it, then maybe you will appreciate Wanderer more.
Wanderer is the only one which I'm using and I appreciate. :)
I haven't found Directory Opus / Magellan comfortable since the Amiga days.
However I'm looking forward for Scalos, which actually looks like the best of the two: it works and feels like the original Workbench but it has a lot of new features and customization like Magellan. That's why I'm keeping an eye on deadwood's progresses on Scalos (I also like the idea to have a minimal Linux distro which has a full "Amiga o.s. / AROS" GUI / user interface).
Anyway, I was thinking that for developers would also be better to use a cross-development environment on the host o.s.. Something like the VisualStudioCode extension that an Amiga fan created for 68K development, which is very productive.
P.S. Actually I have no time to thinker with AROS. I'll try AROS One x86 when I've some time to relax. I really like the work that you're doing with this nice distro.
-
@cdimauro
I agree that a slimmed down "lite" versions for developers with the necessary development tools would be a good idea.
At minimum we would need gcc at the command line, a working & maybe improved version of Murks with some extra features.
Text editors that support syntax highlighting & maybe code completion is also a nice addition. Scintilla based editors are a good starting point.
@AMIGASYSTEM
Magellan has some nice features but it is a large package to deal with. I don't even have the ability to re-compile Magellan. There is a dedicated team for that.
Wanderer on the other hand is quick and easy to use. It is very lean though, lacking many features that are included with Magellan. I especially like "Smart Read" for Magellan which allows reading any file in binary to see the hexadecimal. But I have figured out a way to get Wanderer to do that. Add a menu item to Read Binary. Copy the file to be read into a temp file beginning with "BIN:" but don't add a file extension. Then Wanderer sends the temp filename to an external application (MultiView). But MultiView & the Datatypes system can't recognize the file type so by default it displays hexadecimal. In the future maybe I can figure out how to actually do it correctly but a workaround is good till then.
As far as distros I appreciate all the work that has gone into AROS One x86 as far as file descriptors and window themes, and all the other enhancements. It would be nice if we had some PDF Guides or other detailed documentation about how to make icons & window themes & how to use scripts to install them with some samples. If we could use these enhancements on other distros that would be great. As for custom icons I have found an icon style that I will make part of AROS Vanilla. Though other people may prefer a different style I prefer the IcarosDesktop style of DualPNG Glow Icon. The custom icons that I produce will all be drop-in replacements for IcarosDesktop icons. They will be 46x46 with an image area of 38x38 which leaves 4 pixels on each edge for the gow border on the second image. Other icons that only have one image or that are 48x48 are not suitable for my needs. Besides they wouldn't be compatible with IcarosDesktop. All my icon tools are designed for DualPNG Glow Icons that have two images & the second images has a standard glow border.
So I have chosen to use that style. I have been trying to come up with a cohesive methodology for making icons. I believe I'm almost there. I'm using what I call a "Tile" icon which is 46x46 as described above. It consists of a Squared Icon, usually white but it can be any color, that acts like a button. The Tile has images inserted that can represent whatever the icon is associated with. So a Tile Icon can be used for any icon type that AROS can display such as Tool, Project, Disk, Drawer, etc. All the icons in System: are Tiles. The icons on Workbench Screen that are not Disk Icons are Tile Icons. For third part directories and other directories a simple Folder Icon will be used. The Folder Icon though can only be used for directories (drawers). I prefer to use Folder Icons instead of Drawers because many users coming from Windows or Linux or even Mac OS X will recognize them for what they are. I have already made several icons but I still have many hundreds more to go. They will be available for anyone to use for their own needs when they are all finished.
-
miker "Read" and "Smart Read" also exist on Dopus4, they are internal commands same as magellan.
Inpltre on AROS x86 there is the very good ZAPHOT Hex Editor where you can also easily edit a file, also for the same purpose there is also "HX2", you can find them both on AROS One, folder "Tools", ZAPHOT is already set on Dopus4, see screenshot.
For icon creation I use IconEditor (it exists for both AROS and OS3 and OS4), very simple, you can extract the two images from a DualPNG Icon, you can reduce, add effects and much more all in a simple and intuitive way
For Window Themes you don't need any tutorial, you just need to know how to use a Graphic Editor and modify an existing Theme, of course you have to respect the sizes, the positions lle images and a lot of pasienza to fix the various anomalies, I then am finicky, I intervene even for a single pixel out of place.
For the scripts just look at them, they are very simple, just a few strings, then you reuse the same script by changing only the filename to use.
If you tell me which script is not clear to you, I'll see if I can explain it in simple words and maybe add it in the AROS One manual.
-
i like Magellan but do not use because for me is many complicaded DE ;D
-
Hmmm...problems compiling AROS ABIv11.
-
miker I compiled the toolchain-core-x86_64
-
i used ubuntu 18.04 lts at 64 bit and I followed this
https://github.com/deadw00d/AROS/blob/master/INSTALL.md
-
@miker1264
Which version of Ubuntu are you using? Thins should work with 20.04 and 22.04.
Also please follow the instruction that @Amiwell pasted. It's a standardized way of building and it worked on many configurations already.
-
ah ok dedwood try another version of ubuntu
-
I am using Ubuntu 18.04 I believe. I will verify that.
Those are the instructions I was using.
The x86-64 tool chain built ok. But AROS had an issue.
-
I too have problems compiling on ubuntu 18.04 miker
-
I never understand when I compile the toolchain and contrib source what should I do to compile if anyone can help me I'd be happy at least I'm helpful
-
It's quite possible that it won't work under Ubuntu 18.04. There were some changes in Linux C library which you might have stumbled upon. Best to use 22.04.
-
I never understand when I compile the toolchain and contrib source what should I do to compile if anyone can help me I'd be happy at least I'm helpful
I don't understand. Can you explain what problem are you facing?
-
I wanted to help compile the software, I install everything through your guide then how should I proceed for the compilation
-
example this program how you can compile
http://archives.aros-exec.org/share/audio/record/audioevolution3_src.lha
-
in the terminal what should I write sorry I'm inexperienced
-
Ok, now I understand.
Best is to start with some simple applications. Audioevolution definatelly is not one of them. Select something that has 1-2 source files. There are many resources on the internet that can teach you about basics of using make and gcc. It just requires time and practice to learn.
-
if I have a makefile like for example in games what should I write in the terminal, now I'm creating the toolchain-x86_64, I know how to compile with make but not in the cross environment for aros
-
Cross-compiling is always tricky. Since you already have Linux, why not use AROS hosted and use GCC and make under AROS hosted - this will make things much easier.
-
i thought i was compiling in the source tree, however i got an error compiling core-linux on ubuntu 22.04
-
It's quite possible that it won't work under Ubuntu 18.04. There were some changes in Linux C library which you might have stumbled upon. Best to use 22.04.
After I update Ubuntu to 22.04 do I need to build the tool chain again? Or just try make again?
-
It's quite possible that it won't work under Ubuntu 18.04. There were some changes in Linux C library which you might have stumbled upon. Best to use 22.04.
After I update Ubuntu to 22.04 do I need to build the tool chain again? Or just try make again?
Hard to say. In theory the toolchain should work, but in practice who knows. I think it is better to re-build the toolchain on new installation to avoid some hard to debug problems with it later on.
-
pc-core succesifull compiled
-
pc-core succesifull compiled
Congratulations! Welcome to the club. ;D
I'm attempting to do an in-place upgrade at the linux commandline from 18.04 Bionic Bunny to 20.04 Focal Fossa.
So far all the available packages have been installed.
If all goes well I will do a make to see if it works. Then I will go back to rebuild the toolchain (again!) then make again.
Easy breezy! (I like AROS much better than Linux)
-
AROS is designed for desktop users like the Amiga Workbench :)
-
AROS is designed for desktop users like the Amiga Workbench :)
@Amiwell
Are you using Ubuntu in VMWare for your ABIv11 Build System?
I can help you with compiling some small programs.
Once the Build System is setup it's not difficult to compile.
-
AROS is designed for desktop users like the Amiga Workbench :)
I personally disagree :P
One of the charmes for me is the shell, albeit is showing its age these days. It still has (plugin) features compared to other OS terminals/shells that is unmatched.
But, that is the fun of Amiga OS (and derivatives), you can use it any which way you like. If you are a big Magellan, Scalos, Wanderer fan then you can use that. If you prefer a bourne compatible shell/terminal then you can use that as well. Being able to cherry pick is a nice thing.
-
I suppose I'm the only one who is Linux incompetent?
Why won't it allow me to configure & make AROS for ABIv11 x86-64 ? I built the toolchain for x86-64 successfully.
I have no idea why this isn't working & I'm very busy with other things ATM. I don't think it was this difficult before. >:(
-
Not sure what your order of events is but here are build instruction for ABIv11 (https://github.com/deadw00d/AROS/blob/master/INSTALL.md).
In case you use a cross compiler setup to cross compile small programs then you need to supply a parameter (If i remember correctly it is) named --with-sysroot=/path/to/sysroot
edit: oh it is sysroot (not with-sysroot).
I do not know from memory but if the buildscript does not rerun automatically then start it again using the other preferred selection (you need to build things in the correct order, afaik the script will not do that for you).
-
Not sure what your order of events is but here are build instruction for ABIv11 (https://github.com/deadw00d/AROS/blob/master/INSTALL.md).
In case you use a cross compiler setup to cross compile small programs then you need to supply a parameter (If i remember correctly it is) named --with-sysroot=/path/to/sysroot
edit: oh it is sysroot (not with-sysroot).
I do not know from memory but if the buildscript does not rerun automatically then start it again using the other preferred selection (you need to build things in the correct order, afaik the script will not do that for you).
Thanks. Later I will delete my old sources then start from the beginning.
-
I just verified the build with doing the following:
$ cd /media/ramdisk
$ mkdir work
$ cd work
$ mkdir arosbuilds
$ cd arosbuilds
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cp ./AROS/scripts/rebuild.sh .
$ /usr/bin/time --format='%C took %e seconds' ./rebuild.sh
The shell presents a menu:
rebuild v1.9, select an option:
0) exit
1) toolchain-core-x86_64
2) core-linux-x86_64 (DEBUG)
3) core-pc-x86_64
4) core-contrib-x86_64
5) core-linux-x86_64
11) toolchain-core-m68k
12) core-amiga-m68k
13) core-amiga-m68k (SERIAL DEBUG)
14) core-contrib-m68k
21) toolchain-core-armhf
22) core-linux-armhf (DEBUG)
Because I wanted to verify the build for x86_64, I selected option 1.
After a while that returned:
blah blah from build
./rebuild.sh took 969.47 seconds
And got me a prompt again.
Then I re-ran the rebuild script
$ /usr/bin/time --format='%C took %e seconds' ./rebuild.sh
Again the menu is prompted.
This time we need to select what we want to build (still x86_64).
- for a Linux hosted AROS build, select either 2 or 5
- for building a native 64 bit AROS, select 3
I opted for option 2.
After a while that returned:
blah blah from build
./rebuild.sh took 899.22 seconds
That is where I left things but you could also opt for re-running the rebuild script to try build the x86_64 core contrib.
... Or re-run the rebuild script and select any of the other options that you wish to build for ofc.
Gist of it is you can use the rebuild script to let it build things for you or read the script (and other scripts that it includes) in order to determine the exact process of how AROS is build for a particular target.
If that worked for you then you have a full working standalone AROS cross-compiler and generated the Linux hosted version of x86_64 AROS.
In case wondering: the results are from a 64 bit machine, native running debian testing (bookworm) and rebuild script compiled on/to a 12GB ramdisk. The end result seem to occupies 3.7 GB of files (donwloaded, extracted and/or compiled). Depending on your network connection the time it takes to build may vary.
-
AROS is designed for desktop users like the Amiga Workbench :)
@Amiwell
Are you using Ubuntu in VMWare for your ABIv11 Build System?
I can help you with compiling some small programs.
Once the Build System is setup it's not difficult to compile.
Miker ok I reinstall the system :D, @magorium i have to compile first toolchain-x86_64 then core-pc-x86_64 and core-contrib-pc-x86_64, core-linux-x86_64 (DEBUG) it gives me an error
-
@magorium i have to compile first toolchain-x86_64 then core-pc-x86_64 and core-contrib-pc-x86_64, core-linux-x86_64 (DEBUG) it gives me an error
What error ? (you did not post anything) :)
And when did you got the error exactly ? Only with building the last (e.g. core-linux-x86_64 (DEBUG) ) ?
What platform are you compiling on ?
If it is linux then you could use tee to pipe the output and error to both the terminal and a logfile. The latter could be posted somewhere (or you could copy the relevant failing lines).
edit: There should be an error log somewhere by default but I do not know the exact location/name.
-
now reinstalled the system and did not compile core-linux-x86_64 (DEBUG) only the first mentioned, @miker i have this folder in my system after the compilation
-
@magorium
Ok. I will follow your method. I see a couple things I missed.
-
I tried to compile AROS x86-64 again and again it stops at pci.ids but why?
Does anyone else have this problem? It couldn't find ftdmo2121.zip file either. :'(
-
It tries downloading pci.ids from remote servers (see the log for URLs). Maybe these servers were down when you were building or you had some network issues. Check if you can access the URLs from the build machine.
-
It tries downloading pci.ids from remote servers (see the log for URLs). Maybe these servers were down when you were building or you had some network issues. Check if you can access the URLs from the build machine.
@deadwood
My mistake. It was a bad internet connection. I had to restart the VM for Ubuntu 20.04 for the internet to work.
If nothing else I'm gaining experience compiling sources. :)
Whew! 8)
That took about an hour to complete! See screenshot.
I couldn't get TinyAros to install Hosted On Linux because I couldn't find install.sh or hosted-install.sh and AROS One x86-64 isn't available.
AROS Vanilla (ABIv11) is installed as Native in VMWare which I did test. I tested gcc in a Wanderer shell. In fact I copied the development directory 3 times to make sure!
So to get a Hosted on Linux version to test I compiled it...
-
@deadwood
I installed the development tools for AROS ABIv11 Hosted On Linux (Ubuntu 20.04) & copied Package_Startup to AROS:S directory.
As you can see we now have gcc in the shell. Nice! ;)
But when trying to compile a source file I get an error.
"gcc: error trying to exec 'ccl' : execvp : No such file or directory" So it seems 'ccl' is missing but gcc seems otherwise functional.
By contrast gcc on AROS ABIv11 Native (On WMWare) doesn't even provide the version number which seems like it isn't working at all.
-
By contrast gcc on AROS ABIv11 Native (On WMWare) doesn't even provide the version number which seems like it isn't working at all.
No Miker, on VMware GCC shows correctly the version, see screenshot, there are only problems in compilation, as reported Here (https://ae.amigalife.org/index.php?topic=881.msg15356#new) this morning, Built ABIv11 is full of problems or Bugs.
(https://ae.amigalife.org/index.php?action=dlattach;topic=881.0;attach=4465;image)
-
@miker1264
I prepared for you a hosted package with working GCC: https://axrt.org/development/AROS-20221221-1-linux-x86_64-system-devtools.zip
See screenshot below. The main.c and main.cpp are in the package so you can immediately test if things work.
-
@deadwood
Thanks!
I'm downloading and installing it now. Testing to follow.
I'm using a really slow USB 2.0 Flash Drive.
-
@deadwood
Aha!
AROS Vanilla x86-64 is working well. (It's not really a distro - it's just a test system).
This is what I did. I copied your compiled binaries to a VM. But when I tried to start it using AROSBootstrap it complained that it need an updated graphics lib for Linux.
But I knew that my AROS Vanilla that I just compiled works. So I deleted all the system files except Demos, Extras, Development & S assuming those directories contained the goodies!
Then I copied my AROS Vanilla system files over top of that then strated using AROSBootstrap....and it works! The first Classic Amiga Icon has just exported ILBM to Ram Disk.
I couldn't for some reason compile main.c it complained of missing symbols. But I compiled my IconSplit CLI program and it works beautifully.
So the new gcc in the shell works!
-
Good to know things are working for you now :)
-
Good to know things are working for you now :)
The gcc in the shell is working now so that will speed up compiling & testing small apps.
Now we need a simple text editor with syntax highlighting similar to SciTe then a complete IDE inside AROS. It's on my wish list.
I'm going to keep my Build System separate from the test system. In case I mess things up on one or the other.
It's good that my Build System is up to date and working also. I have a backlog of sources to compile. ;)
-
miker should you need it, my version of AROS One v11 Hosted Linux works fine, to run it you just need to run the file "AROSBootstrap"
-
great miker :)
-
miker should you need it, my version of AROS One v11 Hosted Linux works fine, to run it you just need to run the file "AROSBootstrap"
Could you send me a PM with a download link?
I would like to try it.
Now I have my Build System (cross compiler) setup in Ubuntu 20.04 on the same VM as my Test System for ABIv11. That makes things so much easier and quicker.
The beauty of Ubuntu on VMWare is that I can simply drag-n-drop directly to and from Windows into the VM. I can use the Linux File Manager to quickly move files around and editing in VS Code then dropping it into Linux is a breeze!
I have lots of compiling to do. 8)
-
I will compress the folder and attach you AROS One 64 v11, I can also attach it here, maybe it can be useful to other users.
Question, I tried to compileu V11 your source "IconClone_02-03-23.c", I didn't get any error, but if I try to run "IconClone", I get the message "file not executable", where I am wrong ?
-
I will compress the folder and attach you AROS One 64 v11, I can also attach it here, maybe it can be useful to other users.
Question, I tried to compileu V11 your source "IconClone_02-03-23.c", I didn't get any error, but if I try to run "IconClone", I get the message "file not executable", where I am wrong ?
Me too. I thought gcc was broken. ;D
So I compiled it with the Build System and it works fine. I will post the ABIv11 version & upload it to AROS Archives.
The shell version of gcc on x86-64 still has some issues.
But for really small source files it may be ok.
If you provide a download link I would like to try your x86-64.
-
As soon as I finish uploading to Google Drive I will attach here the link of AROS One 64 Hosted Linux.
However I don't think the problem is the AROS 64 v11 GCC, I tried to compile "IconClone_02-03-23.c" also on AROS One ABIv0 and I get the same error "file not executable"
I suppose there is something in your source that is not supported by the AROS GCC, or some component is missing or needs to be replaced in "Development"
-
As soon as I finish uploading to Google Drive I will attach here the link of AROS One 64 Hosted Linux.
However I don't think the problem is the AROS 64 v11 GCC, I tried to compile "IconClone_02-03-23.c" also on AROS One ABIv0 and I get the same error "file not executable"
I suppose there is something in your source that is not supported by the AROS GCC, or some component is missing or needs to be replaced in "Development"
I compiled IconClone_02-18-23.c with gcc in IcarosDesktop x86. It compiled and worked fine on AROS One x86.
But maybe there is something in it that isn't compatible with other gcc installations. I will try to investigate the issue.
-
Have you used the GCC AROS ? what is Build System ?
-
Have you used the GCC AROS ? what is Build System ?
The Build System is the gcc cross compiler on Ubuntu. It compiles AROS source code using Linux tools. That's the easiest way to compile complex programs like MultiView, LunaPaint, FileMaster & others. It can do small apps also.
The Build System is a larger version of gcc in a shell. It's what the AROS server uses to compile AROS. It's what deadwood uses to compile his new releases for AROS.
-
On what version of Icaros what version of GCC did you use to compile, I would like to do some verification
-
On what version of Icaros what version of GCC did you use to compile, I would like to do some verification
It was IcarosDesktop 2.2.8 x86. Using gcc in a shell. IcarosDesktop uses Magellan. Not sure if that is a factor.
-
I don't think it depends on Magellan, but on a different version of GCC, IcarosDesktop 2.2.8 surely has an old version of GCC, Icaros 2.3 included GCC v4.6.4
-
I don't think it depends on Magellan, but on a different version of GCC, IcarosDesktop 2.2.8 surely has an old version of GCC, Icaros 2.3 included GCC v4.6.4
I was using IcarosDesktop 2.2.8 Hosted on Linux.
I believe the Build System for ABIv11 uses gcc 6.5.0 also. I don't believe the gcc version has much to do with the issue.
It may be an issue with x86 Native vs Hosted just like ABIv11 Native & Hosted for gcc. One works & one doesn't.
Maybe if you copy the Development directory from Icaros 2.2.8 directly into one of your AROS One x86 test system you can test the older gcc in a shell. If it does not work then something else is wrong. If it does work then newer gcc has issues with Native vs. Hosted & x86 vs x86-64.
By simple comparison the startup-sequence is different on Icaros than it is on ABIv11. The Package-Startup on Icaros does not include the assigns for Development directory. Those are located in Startup-sequence near the bottom. On ABIv11 the assign for Development is in Package-Startup.
One last thing then you can do your testing. The difference between a simple source code file & a complex one is not the lines of code or the size in kb. It is the number of includes. For example IconSplit uses no libraries other than studio.h, string.h & the other std library. It has 1500 lines of code but it compiles easily & it works. IconClone however has several system libraries such as IFFParse, Cybergfx, Datatypes, DOS, Exec, Icon & a few others. Maybe gcc has a problem finding the resources the application needs to run.
-
I don't think it's a Hosted version problem, since the GCC of v11 hosted Linux gives the same error on your IconClone source, I ask deadwood to do a check to see where the problem lies.
-
Miker Odyssey could be the first application to work on for porting :)
-
I don't think it's a Hosted version problem, since the GCC of v11 hosted Linux gives the same error on your IconClone source, I ask deadwood to do a check to see where the problem lies.
I can't seem to identify the problem with gcc in the shell not working correctly for every source code file. Some work and some don't.
Until it works perfectly I will use the Build System to compile x86-64 binaries. Here are a few small programs. IconClone (without icon), InfoInfo (cli only), & IconSplit (cli only).
InfoInfo reads an Amiga Classic Icon & gives information in the shell. IconSplit with split an Amiga Classic Icon & save ILBM images in Ram Disk. We know what IconClone does.
-
thanks :)
-
I can't seem to identify the problem with gcc in the shell not working correctly for every source code file. Some work and some don't.
Which shell ? Amiga-shell or sh ?
Note that gcc requires quite a lot of stack, try to increase it.
Any special error messages when a build fails or just silence failure ?
-
I can't seem to identify the problem with gcc in the shell not working correctly for every source code file. Some work and some don't.
Which shell ? Amiga-shell or sh ?
Note that gcc requires quite a lot of stack, try to increase it.
Any special error messages when a build fails or just silence failure ?
The programs seem to compile but some say "not executable".
I increased the stack size to 262144 just because I think that's what Icaros uses. But the same error happens. Not execuatable.
-
@miker:ah, ic. ok.
Compiled programs that result in files that are not executable is a problem of another ballgame. E,g, not really my area of expertise.
Perhaps deadwood knows more about it (although I can understand if he merely has focus for the cross-compiler and not the native (to AROS) one).
-
Now I have my Build System (cross compiler) setup in Ubuntu 20.04 on the same VM as my Test System for ABIv11. That makes things so much easier and quicker.
The beauty of Ubuntu on VMWare is that I can simply drag-n-drop directly to and from Windows into the VM. I can use the Linux File Manager to quickly move files around and editing in VS Code then dropping it into Linux is a breeze!
I have lots of compiling to do. 8)
If you're using Windows then you should seriously try WSL2, which allows to install a Linux Distro (the most important ones are supported, and this includes Ubuntu, of course) on a VM which is transparently integrated on Windows.
For example, I can open a Ubuntu shell directly from the new Windows Terminal (see first attachment)
Or I can access Ubuntu's filesystem from any Windows applications by using the special \\wsl path (see second attachment).
-
The programs seem to compile but some say "not executable".
Try adding -fno-common switch. If this does not help, please share the source code which generates this problem.
-
Try adding -fno-common switch. If this does not help, please share the source code which generates this problem.
Thanks deadwood, -fno-common works !!! now the compiled file is an executable and runs on AROS 64 v11 ;)
@miker
Be careful, on my AROS One 64 v11 that I sent you, it seems that the ZIP compressor has corrupted some files in the "Develpment" folder, I will try to compact it with WinRAR and send it to you, or use the Dvelopment folder attached by deadwood.
(https://ae.amigalife.org/index.php?action=dlattach;topic=1089.0;attach=4609;image)
-
miker i upload your tool icon on archives?
-
Amiwell, I compiled IconClone which you see in the screenshot, when miker will copy it he will decide when to post it on aros archive
--- Italiano ----
Amiwell, ho compilato io IconClone che vedi nello screenshot, quando lo copilerà miker deciderà lui quandio postarlo su aros archive
-
Thanks deadwood, -fno-common works !!! now the compiled file is an executable and runs on AROS 64 v11 ;)
This is a temporary workaround. Next release of contrib archive will have GCC patched so that adding this argument is not needed.
-
Could you send me a PM with a download link?
miker, this is the link where you can download AROS One 64 ABIv11, now the Development folder should work fine, let me know if it works fine for you now.
I deleted the old post with the old link !
On Windows both "ZIP, RAR and 7Zip", when compressing, corrupt the files of the folder "Development", it works fine instead if you compress Development Linux side with "tar.gz"
https://drive.google.com/file/d/1Rq3Sj3S4U9doeLCy29WqfBn-L5vAAoCq/view?usp=share_link
-
Amiwell, I compiled IconClone which you see in the screenshot, when miker will copy it he will decide when to post it on aros archive
--- Italiano ----
Amiwell, ho compilato io IconClone che vedi nello screenshot, quando lo copilerà miker deciderà lui quandio postarlo su aros archive
he also compiled iconclone and other utilities I downloaded in fact moderate the tones with me this behavior of yours does not benefit the community
-
What tone, I simply said that out of respect for Miker I could not post his programs !
---- Ita -----
Quale toni, ho semplicemente detto che per rispetto di Miker non potevo postare io i suoi programmi !
-
miker i upload your tool icon on archives?
I will package the x86 & x86-64 versions to upload later today. They will replace the older versions. Also I wanted to make sure it works well enough on 64bit in case I need to make changes before I release it.
There some anomalies with IconClone on 64bit I'm testing.
-
There some anomalies with IconClone on 64bit I'm testing.
What kind of anomalies did you find ? maybe i do a test with the one i compiled on AROS One 64 v11 GCC, that seems to work well for me.
Have you tried the new archi of AROS One 64 v11 that I attached today ? did it work well ?
-
miker i upload your tool icon on archives?
I will package the x86 & x86-64 versions to upload later today. They will replace the older versions. Also I wanted to make sure it works well enough on 64bit in case I need to make changes before I release it.
There some anomalies with IconClone on 64bit I'm testing.
yes I tried iconclone I wanted to change a png icon did not work
-
I was painting some new colored folder icons for AROS Vanilla.
I wasn't satisfied with using the 'Home' icon for the Workspace. So I hand painted a new one using a blueprint & pencil.
The folder icons are 46x46 with an image size of 42x42. They will have a 2x2 glow border to make them appear slightly larger than project icons.
I may not use all of them. I'm just making lots of them. I will post the icon collections when I finish them if anyone wants to try them.
The Vanilla Icons look nice! A few done, but hundreds more to go. ;)
-
Making Icons is hard work especially if you have to get transparent and quality images, on AROS One the Folder Icons are 780, then consider that I created 4 styles for a total of 3.128 Folder Icons :o
Usually when you reduce images there is a loss of quality, I usually to have no loss of quality I use as "Zoom" the Windows folder, which in the reduction (mouse wheel) reduces with less loss of quality.
The best trick to resize images is to cut/paste by shortening and tightening the images, this greatly decreases the loss of quality.
-
Making Icons is hard work especially if you have to get transparent and quality images, on AROS One the Folder Icons are 780, then consider that I created 4 styles for a total of 3.128 Folder Icons :o
Usually when you reduce images there is a loss of quality, I usually to have no loss of quality I use as "Zoom" the Windows folder, which in the reduction (mouse wheel) reduces with less loss of quality.
The best trick to resize images is to cut/paste by shortening and tightening the images, this greatly decreases the loss of quality.
Indeed it is hard work. It requires many hours to produce quality icons. It's not easy to find or make graphics which scale nicely and look good at icon dimensions. Some need to be "stylized" to make them into an approximation of the real images. The icons are merely symbolic representation of everyday objects or tasks. The more color, the better!
Once I get a complete set of icons that I like I can use HSL Color Rotation to produce more color variations. Overlay masking is useful for automatically copying the images to new colored folder icons. Automation is good. :)
The folder icons will be slightly larger than project icons for visual effects. The project icons are just 46x46 squared Icons usually with a white background but colors vary. I wanted the project icons to be drop-in replacement for PNG Glow Icons such as Kens Icons. They are interchangeable.
The icons that I'm developing for AROS are heavily influenced by the look and feel of early Mac OS X icons, especially the powder blue folder icons. But the graphics also resemble the Faenza Icons for Linux. But as far as I know Faenza are only single PNG or SVG images and they are much larger and different than 46x46 PNG Glow Icons.
Like AROS which has one foot in the past with its Amiga roots and an eye towards the future with a synthesis of things classic and things modern so are the new icons. The PNG icons are modern in appearance but they will be influenced by Classic Amiga Glow Icons from OS3.5/3.9 and especially the visual style of AIAB ( Amiga In A Box ) which used Scalos.
-
It's better to move to a .svgz image so that icon sizes aren't a problem anymore (since those compressed SVG images can be scaled to whatever resolution. IF they are made with good quality).
-
It's better to move to a .svgz image so that icon sizes aren't a problem anymore (since those compressed SVG images can be scaled to whatever resolution. IF they are made with good quality).
That's a good point for a future direction. We can load and save SVG images but I don't think Icon Library can load the SVG icons. Not yet at least.
The problem with an SVG based icon is that's there's no place to store the icon data itself. In PNG icons they use an icOn chunk. Classic Icons store icon attributes in the diskobject data, etc. But SVG would have to be a hybrid icon. Classic Amiga Icon File at the beginning. Where the IFF data for a Glow Icon would normally be is instead the beginning of the SVG data. How many images can it store?
Those are things we would have to investigate.
-
It's better to move to a .svgz image so that icon sizes aren't a problem anymore (since those compressed SVG images can be scaled to whatever resolution. IF they are made with good quality).
That's a good point for a future direction. We can load and save SVG images but I don't think Icon Library can load the SVG icons. Not yet at least.
Yup. It should be updated.
The problem with an SVG based icon is that's there's no place to store the icon data itself. In PNG icons they use an icOn chunk. Classic Icons store icon attributes in the diskobject data, etc. But SVG would have to be a hybrid icon. Classic Amiga Icon File at the beginning. Where the IFF data for a Glow Icon would normally be is instead the beginning of the SVG data. How many images can it store?
Those are things we would have to investigate.
I don't see the problem: those SVGZ icons should be treated like the PNG ones.
SVG is a very flexible format because it allows to embed vector, bitmap and text content, and transformations / filters / animations, so you don't even need to define something like dual PNGs (one SVG should be enough to emulate it).
And to answer to your last question, SVG allows to define metadata of any kind, that can be used to store the icon attributes (and much more). You can add those tags everywhere (AFAIR), so even at beginning of the XML data (this can be "forced" as a requirement for those new icons, if it's needed).
Here are the specs: https://www.w3.org/TR/SVG11/metadata.html
-
The folder icons will be slightly larger than project icons for visual effects.
Attention. on AROS icons with different sizes result in misalignment and clutter among icons, already square icons at the same size as Round icons, will look largie.
Also, folders that have edges or protrusions such as handles will appear smaller, this is why I used different sizes for Icon Sets.
-
The folder icons will be slightly larger than project icons for visual effects.
Attention. on AROS icons with different sizes result in misalignment and clutter among icons, already square icons at the same size as Round icons, will look largie.
Also, folders that have edges or protrusions such as handles will appear smaller, this is why I used different sizes for Icon Sets.
Ah. I'm aware of misalignment issues with icons.
That's why all my icons are 46x46. It's just the image area that changes. Folder image area is 42x42 but regular icon image area just like other AROS Glow Icons is 38x38.
-
For Vanilla Icons rather than the subdued powder blue icons reminiscent of Mac OS X I've decided to go a different route.
Vanilla Icons will be bright and colorful. I started with a forest green icon that I hand painted pixel by pixel in a paint program. Then I applied HSL Color Rotation to produce several color variations. So far I like med blue and med green folder icons.
Let's see how they look on Workbench. :)
-
They are nice, maybe a little small for AROS, great on the other hand for OS3
-
They are nice, maybe a little small for AROS, great on the other hand for OS3
Ken's Icons that are used on Icaros are 46x46 also and they look great. The image area of the drawer icons is less that 38x38 so they look a little small to me.
As far as size comparison I copied a few icons to AROS One. The PNG def icon on the right is part of AROS One x86. The Prefs folder icon is new.
-
Okay, I thought they turned out smaller, a good look !
-
Okay, I thought they turned out smaller, a good look !
I actually like the powder blue icon on AROS One.
The icon in the earlier screenshot was medium blue.
For some reason it looks good. So I produced pastel colors.
The numbers in the filename are HSL Rotation Values.
-
Recently I fixed my Native version of IcarosDesktop 2.2.8 which can now boot correctly in VirtualBox. I had a corrupted picture.datatype that I reloaded from Live DVD.
The Native version is so much nicer than Hosted on Linux. For some reason the X11 driver is very unstable for Hosted
But now I can get back to enjoying Icaros x86 & testing. :)
I have to test IconClone & other software on IcarosDesktop.
Hopefully in the next few weeks I will have some new icons & window themes ready for IcarosDesktop. The icons are just additional & not intended as replacement icons. 8)
-
I am curious to see your Themes, are you using the Theme Editor?
-
I am curious to see your Themes, are you using the Theme Editor?
I haven't made any yet. ;)
I'm interested in the Whistler Watercolor Themes and some modified blue, gray and green themes (matte not glassy). For the Watercolor themes I would place the close gadget on the left side though to be consistent with Amiga/AROS.
As for the new glow icons for Icaros I have Silver Edition Two-Tone Drawers, Assorted Colored Drawers some with blue or green glow borders, various other drawers and some other random glow icons mostly for documents & pictures.
-
The closing gadgets you can place them wherever you want, just a small modification to the configuration script is enough.
The Whistler Watercolor Themes is nice, but you will have to adapt it for AROS, I have never used the Theme Editor, if you decide to do it by hand it will be a very hard job to make the gadgets match !
-
I'm still working on some new icons. 8)
In the first image you see that the Blue folder icons has a nice glow border but it's only 2x2 pixels instead of 4x4 for Icaros Icons. The def_png icon is from AROS One for comparison.
The Aqua folder icons to the left will also be available. The image area for folders is 42x42 instead of 38x38 making them appear larger though the icons themselves are still 46x46.
Notice the visual difference in size of the two new Wanderer icons. ( the cat logo was Kalamatee's idea a few years ago! ).
The smaller Icaros compatible icon seems visually better than the larger icon though they are both 46x46. I will produce both sizes - one for Icaros & Vanilla as well as one for AROS One.
-
Miker is possible to port zuneview and zunepaint on abiv11