Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impossible to build with sconsolidator when scons works fine #13

Open
sverley opened this issue Jul 1, 2014 · 1 comment
Open

Impossible to build with sconsolidator when scons works fine #13

sverley opened this issue Jul 1, 2014 · 1 comment

Comments

@sverley
Copy link

sverley commented Jul 1, 2014

Hi,

I am trying to configure sconsolidator to compile my project, but I can't figure it out.

When I launch scons in the terminal session, the project compile successfully as well as in eclipse by modifying the C++ builder configuration (make -> scons).

When I try to convert this project into scons project, the lauch command is more complex than the one I use to use and the building process never ends.

scons prod=eos-intel

becomes

/usr/local/python/bin/scons -u -s prod=eos-intel -f SConstruct -f /stck3/stck3.1/sverley/CODES/elsA/v3.5.02-parallel_move3d/Kernel/BuildInfoCollector.py --directory=/stck3/stck3.1/sverley/CODES/elsA/v3.5.02-parallel_move3d/Kernel

If I copy/paste this command line in the terminal session, I have the following error :

scons: warning: Ignoring missing SConscript 'BuildInfoCollector.py'
File "/usr/local/python/bin/scons", line 190, in <module>
/usr/bin/cpp  -D_ELSA_COMPILER_INTEL_IA32em_ -DE_SCALAR_COMPUTER -D_E_USE_STANDARD_IOSTREAM_ -DE_RTTI -DE_MEMORY   -D_E_FORTRAN_LOOPS_ -DE_DOUBLEREAL -UE_DOUBLEINT -DCAPS_UNROLL -DCAPS_SPEC -DCAPS_REMOVE_COND -DCAPS_SPLIT_LOOP -DCAPS_REMOVE_DIVIDE -DCAPS_DIRECTIVES -D_ELSA_COMPILER_INTEL_IA32em_ -DE_USE_LAPACK  -DE_ELSA_CONFIG_FILE   -I/stck3/stck3.1/sverley/CODES/elsA/v3.5.02-parallel_move3d/Kernel/src/Api/Modules -I/stck3/stck3.1/sverley/CODES/elsA/v3.5.02-parallel_move3d/Kernel/.scons.eos-intel.tmp/build/src -I/usr/local/python/lib/python2.7/site-packages/mpi4py/include -I/usr/local/cgns-intel-3.1.3/include -I/stck3/stck3.1/sverley/CODES/elsA/v3.5.02-parallel_move3d/Kernel/src -I/usr/local/python/include/python2.7 -I/usr/local/python/include/python2.7 -I/usr/local/python/lib/python2.7/config  -traditional-cpp -P -C  .scons.eos-intel.tmp/build/src/Opt/Adjeq/OptAdj_Wall_RoeO1_slipF.for > .scons.eos-intel.tmp/build/src/Opt/Adjeq/OptAdj_Wall_RoeO1_slipF.F
OSError: [Errno 2] No such file or directory:
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Script/Main.py", line 1271:
    _exec_main(parser, values)
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Script/Main.py", line 1236:
    _main(parser)
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Script/Main.py", line 1000:
    nodes = _build_targets(fs, options, targets, target_top)
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Script/Main.py", line 1194:
    jobs.run(postfunc = jobs_postfunc)
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Job.py", line 113:
    postfunc()
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/Script/Main.py", line 1191:
    SCons.SConsign.write()
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/SConsign.py", line 109:
    syncmethod()
  File "/usr/local/python-2.7.5/lib/scons-2.0.1/SCons/dblite.py", line 125:
    self._os_rename(self._tmp_name, self._file_name)
Exception OSError: OSError(2, 'No such file or directory') in <bound method dblite.__del__ of <SCons.dblite.dblite object at 0x5a04fd0>> ignored

How do I have to set up scons to make it works ? Why does it add the -s option ?

@mrueegg
Copy link
Contributor

mrueegg commented Aug 25, 2015

SConsolidator needs the additional command line arguments in order to run a Python script which collects the necessary include paths and macros for your build in order to be able to add it to the CDT project settings.

Your command line does not work because SCons is not able to find the Python file BuildInfoCollector.py which is provided by the plug-in, but deleted after the build is run.

You can run the command by copying this file somewhere to your hard disk and by passing the path as a command line argument.

The output of this command would very much help in finding the root cause of the issue you mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants