loke56 / swtoolkit

Automatically exported from code.google.com/p/swtoolkit
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Toolkit will not build on FreeBSD #22

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Setup a FreeBSD system.
2. Install the prerequisites.
3. Proceed to install swtoolkit.

What is the expected output? A build of swtoolkit What do you see instead?#     
 using distcc.
#   -s -k
#      Don't print commands; keep going on build failures.

export SCT_DIR="$(dirname -- "${0}")"
export PYTHONPATH=/usr/local/lib/scons-1.3.0/SCons

# Invoke scons via the software construction toolkit wrapper.
python $COVERAGE_HOOK "${SCT_DIR}/wrapper.py" $HAMMER_OPTS 
--site-dir="${SCT_DIR}/site_scons"
"$@"
:q!
# scons

scons: *** No SConstruct file found.
File "/usr/local/lib/scons-1.3.0/SCons/Script/Main.py", line 858, in _main
# sh *sh
Traceback (most recent call last):
  File "./wrapper.py", line 44, in <module>
    import SCons.Script
ImportError: No module named SCons.Script
# locate SCons.Script
# 

What version of the product are you using? The recent and only release. On what 
operating system? FreeBSD.

Please provide any additional information below.
Currently building- or trying to build on i386. Further building attempts will 
also be on powerpc and sparc64 machines.

I'm trying to port something similar to googletalk plugin for the BSD systems.
Hammer.sh was edited to include the actual path of SCons.
Main.scons is located in samples, while the path of site_scons has only python 
files.

Original issue reported on code.google.com by outro.pe...@gmail.com on 23 Jan 2012 at 11:10

GoogleCodeExporter commented 8 years ago
I'm having the same (first) problem using cygwin. But with scons-2.2.0...

scons: *** No SConstruct file found.
File "/lib/scons-2.2.0/SCons/Script/Main.py", line 905, in _main

Original comment by viipe....@gmail.com on 25 Aug 2012 at 10:22

GoogleCodeExporter commented 8 years ago
Has there been a resolution for this issue im building google omaha and are 
getting the same issue.

Original comment by jackgarc...@gmail.com on 4 Nov 2013 at 2:45