dev:gettingstarteddunegitneptus

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
dev:gettingstarteddunegitneptus [2018/09/19 15:09] – created albertodev:gettingstarteddunegitneptus [2023/09/06 11:21] (current) – external edit 127.0.0.1
Line 15: Line 15:
 </code> </code>
 ==== DUNE ==== ==== DUNE ====
-All code and shared files are placed on a gitlab repository. You can find it here: [[http://uavlab.itk.ntnu.no:88/uavlab/dune|UAVlab Git]]. To get the code yourself, you clone it into your chosen folder.+All code and shared files are placed on a gitlab repository. You can find it here: [[https://gitlab.com/aurlab|AURlab Git]]. To get the code yourself, you clone it into your chosen folder.
  
 <code> <code>
-mkdir uavlab +mkdir aurlab 
-cd uavlab +cd aurlab 
-git clone git@uavlab.itk.ntnu.no:uavlab/dune.git+git clone https://gitlab.com/aurlab/lsts_toolchain/dune.git
 cd dune cd dune
-git clone git@uavlab.itk.ntnu.no:uavlab/dune-ntnu.git user 
-cd ../ 
 mkdir build mkdir build
 cd build cd build
-cmake -G "Eclipse CDT4 - Unix Makefiles" ../dune+cmake ../dune
 make -j8 make -j8
 </code> </code>
Line 36: Line 34:
 Now, clone and build Neptus. Now, clone and build Neptus.
 <code> <code>
-cd uavlab +cd aurlab 
-git clone http://github.com/LSTS/neptus+git clone https://gitlab.com/aurlab/lsts_toolchain/neptus.git
 cd neptus cd neptus
 ant ant
Line 45: Line 43:
  
 <code> <code>
-sh neptus+./neptus
 </code> </code>
  
Line 54: Line 52:
  
 <code> <code>
-cd uavlab+cd aurlab
 cd dune cd dune
-cd user 
 git checkout -b feature/your_descriptive_branch_name git checkout -b feature/your_descriptive_branch_name
 </code> </code>
-Now you should have moved to your own branch. Every time you make something new on your branch, or do some major updates (minimum once a day), you should commit your changes. Read more on [[dev:git|Developing with GiT]]. +Now you should have moved to your own branch. Every time you make something new on your branch, or do some major updates (minimum once a day), you should commit your changes.
 You should have your own config file, and you make it by right-clicking on the // /etc//-folder and choose //new//->//File//. Name your file //name.ini//. In your config file you can include the tasks that you need to run, and specify the parameters for each task.  You should have your own config file, and you make it by right-clicking on the // /etc//-folder and choose //new//->//File//. Name your file //name.ini//. In your config file you can include the tasks that you need to run, and specify the parameters for each task. 
  
  • dev/gettingstarteddunegitneptus.1537362592.txt.gz
  • Last modified: 2023/09/06 00:32
  • (external edit)