Skip to main content

[s2plot] Installing S2PLOT on Ubuntu 14.04 LTS 64bits

Source code from S2PLOT:http://astronomy.swin.edu.au/s2plot/versions/s2plot-3.2.1.tar.bz2

Thanks for Navtej's BLOG, I almost follow his tutorial.

Besides the issues mentioned in his blog, I also refer to this github.

#This tutorial is used to reappear their guides
#I executed all the following steps in root mode.

-----------------------------------

  1. Download the latest version of S2PLOT from official S2PLOT website.
  2. Install the essential packages:
    sudo apt-get install libhpdf-2.2.1 libhpdf-dev freeglut3 
    freeglut3-dev libfreetype6 libfreetype6-dev libgd2-xpm-dev g++
  3. Extract the file to a directory where you want. 
  4. Follow the INSTALL.txt, I plan to install it under /usr/local/s2plot 
  5. build.csh is the only file we have to take care, as it executes the other scripts automatically.
  6. Then set up the essential environment variables:
  7. export S2PATH=/usr/local/s2plot
    export S2ARCH=linux-gnu-x86_64 
    export S2SHARED=yes
    export S2FREEGLUT=yes
    export S2FREETYPE=yes 
    export S2PLOT_PRCDRIVER=s2prcwriter  
  8. In s2plot.csh, change
    set S2X11PATH=/usr/X11R6
    to
    set S2X11PATH=/usr
  9. In linux-gnu-x86_64.in, change COMPPATH to the place of your gcc. In general, you can change it to
    set COMPPATH="/usr/bin"
  10. Run ./script/build.csh 
  11. Two potential issues as mentioned in Navtej's BLOG, the procedure may fail while linking S2view program. He gave a solution that changing the following lines in build-viewer.csh :
    $S2CLINKER -o s2view geomviewer.o -L. ${S2LINKS} ${MLLINKS} 
    ${SWLINKS} ${GLLINKS} -L${S2X11PATH}/lib${S2LBITS} 
    ${S2FORMSLINK} -lXpm -lX11 ${IMATH} -lm ${XLINKPATH}
    
    to
    $S2CLINKER -o s2view geomviewer.o -L. ${S2LINKS} ${MLLINKS} 
    ${SWLINKS} ${GLLINKS} -L${S2X11PATH}/lib${S2LBITS} 
    ${S2FORMSLINK} -L/usr/lib/x86_64-linux-gnu -ldl -lXpm -lX11 
    ${IMATH} -lm ${XLINKPATH}
  12. Another one is the error that it is not able to find libXpm on your machine.
    sudo ln -s /usr/lib/x86_64-linux-gnu/libXpm.so.4 /usr/lib/x86_64-linux-gnu/libXpm.so
  13. In case that you got a error message like "::too many arguments ", Set
    S2LIBINDEX="ranlib" instead of S2LIBINDEX=":" in scripts/linux-gnu-x86_64.in.
  14. Executable files will be generated in "/usr/local/s2plot-3.2.1/linux-gnu-x86_64". Then you can run the examples with the following commands from /usr/local/s2plot-3.2.1 directory:
    ./linux-gnu-x86_64/s2view
    ./linux-gnu-x86_64/ns2thwcube




Comments

Popular posts from this blog

RSB+RTEMS 5/6 with QEMU-SMP (ARM realview_pbx_a9_qemu as example)

Since I got a request regarding this blog  written in 2016, summarizing again the complete flow with the latest version of RTEMS could be a good idea. Prepare a suitable workspace according to the adopted operating system on your host ( https://docs.rtems.org/branches/master/user/hosts/index.html ):  sudo apt-get build-dep build-essential gcc-defaults g++ gdb git unzip pax bison flex texinfo unzip python3-dev libpython-dev libncurses5-dev zlib1g-dev Checkout RSB and build: git clone git://git.rtems.org/rtems-source-builder.git rsb change directory to rsb/rtems/ and type ../source-builder/sb-set-builder --prefix=<the path you like to store the built toolchains> <the name of bsp> For example, to use QEMU, I need toolchains for ARM, so: ../source-builder/sb-set-builder --prefix=/home/kh.chen/respository/build/. 6/rtems-arm This will take a while. Please ensure your connection is reliable. Add the built folder into your PATH. For example, you can add one line in ~/.bas...

[LEGO nxt] Install the Enhanced NXT firmware and Upload the OSEK excutable file with Ubuntu 64bits 14.04 in 2015

This tutorial is referred from Install the Enhanced NXT firmware on NXT . I think this is the critical part to capture the idea from the tutorial for Windows. I have tried many ways to conquer the problem of libnxt3.0, however, I still have some problems on the compilation of fwflash or something else. Though the tutorial for Windows is doable, my preference is to build up everything with Linux environment. Fortunately, I notice that NxTTool in the tutorial for Windows is really powerful. We can handle the firmware updating by using NxTTool in Linux as well! I also refer to this Japanese Blog , which inspire me a lot. As usual, install the required packages: sudo apt-get install libusb-dev:i386 libusb-0.1-4 subversion fpc Please note, here is the case for 64bits user that I change libusb-dev to libusb-dev:i386 comparing to the original tutorial. Instead of using libnxt to do the uploading, here I follow that JP Blog to get the latest version of bricxcc: (The url in blog i...

Virtualenv experience or alternatives

Today I have a project which requires several packages on my python. However, due to whatever reason, I have a lot of different versions of python. Before I thought, it was fine to just install and maintain each by each. Maybe it is time to learn how to use virtualenv. (alternatively, you can use module). I first got some quick ideas from here: https://stackoverflow.com/questions/10763440/how-to-install-python3-version-of-package-via-pip-on-ubuntu The magic virtualenv does is that, it copies a series of your python binaries, include, pip, etc., into a folder. The prepared activate script does that, add the export folder into the general variable PATH at its beginning. By doing so, the targeted version of python will be the first target that will be executed. To enable virtualenv, source the position of the above folder/bin/activate To leave the virtualenv, just type deactivate, as it is defined when you load the activate script. For example, I call virtualenv in my home ...