Compiling open sour...
 
Notifications
Clear all

[Solved] Compiling open source automaker?

   RSS

0
Topic starter

Great news that automaker software comes under an open source licence now. I had to have a go at compiling to become familiar with it but couldn't get any further than compiling configuration in netbeans (which I have never used before but get the gist of) because of dependencies of the other files on configuration. I do like to tinker and learn and may be able to further development.

However, I'm not familiar with compiling java and the environment settings. As this is on git which I cloned, do I have have to change anything regarding repositories to be stand alone or how can I compile with the dependencies? Apologies for this rather noobish question, but it's something I'm not familiar with and it makes sense to ask here. 

Many thanks, 

Hnnrs 

 

Edit: apologies if this is in the wrong section of the forum

This topic was modified 2 months ago by hnnrs1092
5 Answers
0
Topic starter

SOLVED

Hi All,

Managed to compile after firing a few neurons! Version number for each dependency needed to be correct ie target configuration was version 1.4 once compiled but 1.3 in the pom file of Stenographer. Silly me.

Hnnrs

0

Hi! Congratulations!
Can you tell us/my which Java IDE you used?
Or a little tutorial that you could also become successful yourself?!

Thanks!

0
Topic starter

Hi,

As outlined in the readme file I have used NetBeans. I had to include the plugins to use it. I downloaded automakerOS as a zipfile as I couldn't clone the code. I also had to change the mop.xml file in Stenography to reflect the configuration version (1.4 instead of 1.3) and target version (1.11 instead of 1.10). Just follow the readme. It's not too difficult. I renamed the .jar file and lib folder in automaker in case I needed to return to the original files and used drag and drop to put the new files in place rather than use the command line (easier to do). GCodeViewer is missing files and doesn't compile but for some reason the original worked in linux. I've posted more details of 'how' in the facebook 'unofficial' users robox site.
Hope that helps.
hnnrs

0

Hi!

Thanks a lot!!! I had also found out that I need Netbeans. I didn't read the readme file before. (stupid)
After 2 days I have now managed to compile completely. But only under Linux with english language version. The Linux version seems to be fully functional (AutoMaker & GCodeViewer) ,I think. And it seems that it also works fully under Windows.
Everything else then in the Facebook group.
Thanks again!

Greetings!!

0
Topic starter

Hi Steffen,

Great to hear of your success! The challenges will be making improvements to Automaker with more options for cura etc.

All the best,

hnnrs

Some of this is compromised by the JavaFX GUI, which won't allow some option enabling, as it stands :)
I also downloaded Netbeans earlier today, I think it was the standard 12.2 397Mb version, so will look at the other options before I compile. I know Henry Gibson spotted the pom.xml version number issue that stopped the compilation, but he has got Linux (Ubuntu) & macOS versions of GCodeViewer to run too. I'm still modding my "clone", but well done to all so far.

Share:

This community page and the content inside is publicly visible except in restricted groups. A registered community member is able to post content. Because of the open nature of this forum the content posted may not represent the views of CEL. While we do regularly read the content posted, in some cases the content may not be appropriate for the reader or may cause offence. Please help us by reporting such content. Technical advice provided in this forum may be provided with good intention and a belief that is is correct but may not be applicable to all hardware, software or user ability. In some cases content may not be relevant to newer or older revisions, conflicting or incorrect advice may be contained within conversations, community moderators will attempt to add to this or make corrections but to preserve the thread this may be on following pages or be missed as the forum evolves.

For official advice users should contact the CEL support team via www.cel-robox.com/support/ and follow the provided advice to preserve safety, warranty and function of Robox hardware or software.
This applies to any use or alteration which is not specifically described in the officially supplied guides from CEL. Community content should not be considered official even where posted by CEL employees. Only advice provided via the CEL support portal should be considered official.
Robox is a complex machine with many potential uses, to help preserve the good working order of both hardware and software please be patient and note that many common fixes for other 3D printers do not apply to Robox and may cause irreversible damage or compromise safe operation.
Images and content placed on this forum may be used by CEL and in related media without reward or attribution.