[Camino-users] compile Camino

[Hall, Matt]

Hi Stefania,


Thanks for your mail. This is not correct. The Makefile construct all the .class files, calling javac as appropriate. Step 1 is superfluous. There is nothing you need to do to change the Makefile. Step 2 is superfluous. You only need step 3.


This is pretty standard for building a project like camino, and nothing unusual in this -- it's the way build tools work. I recommend having a look for a java development tutorial which will teach you about the process.


Matt.

________________________________
From: stefania oliviero <stefania.oliviero at hotmail.it>
Sent: 06 June 2017 10:44:07
To: Hall, Matt; camino-users at www.nitrc.org; Jonathan Rafael Patiño
Subject: Re: compile Camino

Dear all,
thank you Matt and Jonathan for all your precious suggestions... Now I know what I have to do.


  1.  create .class files for all the modified and new .java files using commandline: es.

                                                                                                              $ cd camino
                                                                                                              $  javac tools.CL_Initializer.java
                                                                                                                  ...  and doing debug
       2. control makefile : in my case I don't modify it
       3. compile Camino using "make" on the commandline

Cheers

Stefania


________________________________
Da: Hall, Matt <matt.hall at ucl.ac.uk>
Inviato: lunedì 5 giugno 2017 15.51.16
A: stefania oliviero
Oggetto: Re: compile Camino


If the files are referenced from code which is already being compiled, you should put them in the folder indicated by the package structure you've declared at the top of the source. The compiler will then find them itself. There's no need to add every source file explicitly to the build path or the makefile unless you're building  a completely new command.


I assume since you're adding new substrate fies that this is all part of the existing simulation framework, which is part of the datasynth command. as long as the folder structure is legal in java (i.e. simulation.substrates.elements.NewElement lives in simulation/substrates/elements and is called NewElement.java etc) the compiler will know where to look.


once you've got a clean compile you can run the usual simulation command you'd normally use to test the code.


hope this helps,

Matt.

________________________________
From: camino-users-bounces at www.nitrc.org <camino-users-bounces at www.nitrc.org> on behalf of stefania oliviero <stefania.oliviero at hotmail.it>
Sent: 05 June 2017 12:53:28
To: camino-users
Subject: [Camino-users] compile Camino


Dear all

I am working on the introduction of a new substrate and so, I  changed some  .java files and introduced some new ones.

Once the code rewrite is complete, what should I do to debug and compile the new version of camino and make it executable?


ps. At the moment I'm using text editor and ECLIPSE to control simple lines of code, but I don't know its functions ...

Thanks

I'm sorry for my ignorance ...

Thank you

Stefania Oliviero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.nitrc.org/pipermail/camino-users/attachments/20170606/af2bf02f/attachment.html>