rjud / jud

Chain for toolchain : download, configure, build, test, submit, install, pack and upload a series of applications.

jud

Chain for toolchain : download, configure, build, test, submit, install, pack and upload a series of applications.

jud's Issues

Allow to deploy in another directory than $install

Rename to srcdir after checkouting

because the command may fail

Add build_depends_on

example to load perl in the PATH
build_depends_on Perl

Support update function

It would be sweat to support this kind of interface:

jud.rb update <project>
jud.rb update <project> --follow-dependencies

This could fetch the latest of version of the sources and rebuild/follow dependency rebuilds for the project.

❤️

pb (c)make configuration

I ended up with a configuration file containing:

CMake Native Build Tool: Jud::Tools::Make

instead of

CMake Native Build Tool: Make

After recompiling a project, show what should be recompiled

Rethink deployment

Deployment should not be decided by project but by application. An application should decide to install some projects in a specific common directory. Deployment should be reserved to execution (and to development). Only binaries and shared data should be present in this common directory.

cannot load such file -- workspace/jud/Tools/jud::tools::make.rb

Generate execution environment

We should have a way to easily set up $PATH, $LD_LIBRARY_PATH and $PYTHONPATH using the application installation directory.
Below is an example of a manually written script to do that.

#!/bin/bash

# Absolute path to this script
SCRIPT=$(readlink -f "$BASH_SOURCE")
# Folder containing this script
INSTALL_PATH=$(dirname "$SCRIPT")
echo "Using $INSTALL_PATH as install path"

# Application-specific environment variables
export MY_APP_VARIABLE=$INSTALL_PATH

# Environment variables common to all applications
export PYTHONPATH=$INSTALL_PATH/usr/lib/python2.7/site-packages:$PYTHONPATH
export LD_LIBRARY_PATH=$INSTALL_PATH/usr/lib:$LD_LIBRARY_PATH
export PATH=$INSTALL_PATH/usr/bin:$PATH 

Specify --build_type on the command line

Issue in pack_tool (missing include ?)

Unpack swigwin-2.0.11.zip to install-msvc12/main/Swig-win32-x86
AppData/Local/Temp/ocr560E.tmp/src/jud/src/Library/pack_tool.rb:25:in unpack': uninitialized constant Jud::Tools::ZipTool (NameError) from AppData/Local/Temp/ocr560E.tmp/src/jud/src/Library/project.rb:649:inunpack_this'

Associate configuration files to computer

The conf files in .jud should be sharable between several computers.

Test SDK 7.0A or 7.1A

Zip doesn't work

src/jud/src/Library/pack_tool.rb:25:in unpack': uninitialized constant Jud::Tools::ZipTool (NameError) from src/jud/src/Library/project.rb:649:inunpack_this'
from src/jud/src/Library/project.rb:135:in `install_me'