shauwe / typhoon-blade Goto Github PK

开启C++11: 
在配置文件cc_config节确保加上cxxflags='gnu++0x'参数即可：cc_confi
g(cxxflags='gnu++0x')

should be:

开启C++11: 
在配置文件cc_config节确保加上cxxflags='-std=gnu++0x'参数即可：cc_
config(cxxflags='-std=gnu++0x')

or -std=gnu++11 depends on gcc version

mac os不支持readlink 
-f，但是blade的构建使用到了这个，所以会提示报错然后找不�
��对应的相关文件。

cd the directory example and run the command "blade build ...",
then I get this error message: 
Blade(info): loading BUILDs...
Blade(error): //proto:contact_proto: target //#:protobuf does not exists

I read the wiki and the blade.conf but I do not know how to fix the protobuf 
path yet!
I install the protobuf already and can complie the example of google protobuf 
with this command:
g++ -o test test.c first.pb.cc -lprotobuf -pthread

But the blade  just cann't  work! The configure  about protobuf is like this:
 19     proto_library_config(
 20     protoc='protoc',
 21     protobuf_libs=['#protobuf', '#glog', '#gflags', '#pthread'],
 22     protobuf_path='thirdparty',
 23     protobuf_include_path = 'thirdparty',
 24     )

When I delete this part from th blade.conf, it doesn't work yet!
My protobuf is installed in the default directory: /usr/local/

What's the problem about my configure file. Hope I have described my question 
clearly.
If you have any idea, I really appreciate to hear that! 
Thanks a lot!

null

blade/blade build thirdparty/gtest/...


lade(info): ccache found
Blade(info): loading BUILDs...
Blade(info): loading done.
Blade(info): analyzing dependency graph...
Blade(info): analyzing done.
Blade(info): generating build rules...
Blade(warning): thirdparty is not under version control
Blade(info): generating done.
Blade(info): tunes the parallel jobs number(-j N) to be 4
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
scons: building associated VariantDir targets: build32_release
Compiling thirdparty/gflags-2.0/src/gflags.cc
Compiling thirdparty/gflags-2.0/src/gflags_reporting.cc
Compiling thirdparty/gflags-2.0/src/gflags_completions.cc
Compiling thirdparty/glog-0.3.2/src/demangle.cc
Compiling thirdparty/glog-0.3.2/src/logging.cc
Compiling thirdparty/glog-0.3.2/src/raw_logging.cc
Compiling thirdparty/glog-0.3.2/src/signalhandler.cc
Compiling thirdparty/glog-0.3.2/src/symbolize.cc
Compiling thirdparty/glog-0.3.2/src/utilities.cc
Compiling thirdparty/glog-0.3.2/src/vlog_is_on.cc
Compiling thirdparty/gperftools-2.0/src/base/logging.cc
Compiling thirdparty/gperftools-2.0/src/base/dynamic_annotations.c
Compiling thirdparty/gperftools-2.0/src/base/spinlock.cc
Creating Static Library build32_release/thirdparty/glog-0.3.2/src/libglog.a
Ranlib Library build32_release/thirdparty/glog-0.3.2/src/libglog.a
Compiling thirdparty/gperftools-2.0/src/base/spinlock_internal.cc
Compiling thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.cc
In file included from thirdparty/gperftools-2.0/src/base/atomicops.h:101:0,
                 from thirdparty/gperftools-2.0/src/base/spinlock_internal.h:40,
                 from thirdparty/gperftools-2.0/src/base/spinlock_internal.cc:43:
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h: In function 'void 
base::internal::SpinLockDelay(volatile Atomic32*, int32, int)':
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm7' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm6' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm5' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm4' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm3' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm2' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm1' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:390:67: error: 
unknown register name 'mm0' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm7' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm6' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm5' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm4' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm3' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm2' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm1' in 'asm'
thirdparty/gperftools-2.0/src/base/atomicops-internals-x86.h:367:67: error: 
unknown register name 'mm0' in 'asm'
scons: *** 
[build32_release/thirdparty/gperftools-2.0/src/spinlock.objs/base/spinlock_inter
nal.cc.o] Error 1
scons: building terminated because of errors.
Blade(error): building failure

An Android engineer working at Google requested this when he saw my promotion 
of Blade on Google+.

http://code.google.com/p/typhoon-blade/wiki/GoogleLibs中提到的
所有的库都有两个目录，libname-1.6.0 和 
libname，前者是为了升级使用的，请不要用，只用不带版本的�
��录。
-----------------------------
请问libname目录如何从libname-1.6.0中剥离出来？需要做哪些？知
识吧头文件弄出来吗？还是？请指教：）谢谢

在ubuntu 12.0下执行blade test -j4 ...后，提示如下错误： 

Blade(info): ccache found Blade(info): loading BUILDs... Blade(error): 
//thirdparty/gtest:gtest_test: target //#:gtest_main does not exists

P.S.:在这里再贴下，方便其他人看到

I run the command "svn checkout http://typhoon-blade.googlecode.com/svn/trunk/ 
typhoon-blade-read-only" 
but got an empty directory....what's wrong with me, and can you help me get the 
source?
Thanks a lot!

When I use a simple BUILD file:

c_binary(
    name='a',
    srcs=['a.cc'],
    deps=['#pthread','#dl'],
)

to build a simple C++ program 

#include <iostream>

int main() {
  std::cout << "Hello World!\n";
  return 0;
}

on my Mac OS X with XCode 4.6 using the following command:

~/blade build --verbose

I can see the command by blade to invoke g++:

$g++ -o a.cc.o -c -Wno-invalid-offsetof -Woverloaded-virtual -Wnon-virtual-dtor 
-Werror=non-virtual-dtor -fPIC -Wall -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -Wendif-labels -Wfloat-equal -Wformat=2 
-Wmissing-include-dirs -Wpointer-arith -Wwrite-strings -Werror=char-subscripts 
-Werror=comments -Werror=empty-body -Werror=endif-labels -Werror=format 
-Werror=format-nonliteral -Werror=missing-include-dirs -Werror=non-virtual-dtor 
-Werror=overflow -Werror=overloaded-virtual -Werror=parentheses -Werror=reorder 
-Werror=return-type -Werror=sequence-point -Werror=sign-compare -Werror=switch 
-Werror=unused-label -Werror=unused-value -Werror=unused-variable 
-Werror=write-strings -m64 -pipe -g -DNDEBUG -D_FILE_OFFSET_BITS=64 -O2 
-fno-omit-frame-pointer -Ithirdparty -Ibuild64_release -I. 
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 
a.cc

And unfortunately, it seems that the compiler flags implies too strict code 
style check that even the standard C++ library cannot pass the check:

cc1plus: warning: thirdparty: No such file or directory
cc1plus: warning: build64_release: No such file or directory
In file included from /usr/include/c++/4.2.1/locale:46,
                 from /usr/include/c++/4.2.1/bits/ostream.tcc:46,
                 from /usr/include/c++/4.2.1/ostream:635,
                 from /usr/include/c++/4.2.1/iostream:45,
                 from a.cc:1:
/usr/include/c++/4.2.1/bits/locale_facets.tcc: In member function '_InIter 
std::money_get<_CharT, _InIter>::_M_extract(_InIter, _InIter, std::ios_base&, 
std::_Ios_Iostate&, std::string&) const':
/usr/include/c++/4.2.1/bits/locale_facets.tcc:1388: error: suggest a space 
before ';' or explicit braces around empty body in 'for' statement
/usr/include/c++/4.2.1/bits/locale_facets.tcc:1469: error: suggest a space 
before ';' or explicit braces around empty body in 'for' statement
/usr/include/c++/4.2.1/bits/locale_facets.tcc:1481: error: suggest a space 
before ';' or explicit braces around empty body in 'for' statement

~/bin/make2build is a bad link, because there is no 'make2build' script file in 
source directory.

提示如下：

Blade(info): Welcome to blade2
Blade: Entering directory `/home/fandywang/project/google-libs'
Blade(info): ccache found
Blade(info): loading BUILDs...
Blade(info): loading done.
Blade(info): analyzing dependency graph...
Blade(info): analyzing done.
Blade(info): generating build rules...
Blade(warning): thirdparty is not under version control
Blade(info): generating done.
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
scons: building associated VariantDir targets: build64_release
version information updated
Linking Program build64_release/thirdparty/protobuf-2.4.1/src/protoc.bin
scons: done building targets.
Blade(info): spawn 1 worker(s) to run tests
Blade(info): blade test executor 0 starts to work
Blade(info): Running thirdparty/perftools/tcmalloc_test
WARNING: Perftools heap leak checker is active -- Performance may suffer
Running main() from gtest_main.cc
[==========] Running 7 tests from 2 test cases.
[----------] Global test environment set-up.
[----------] 4 tests from TcmallocDeathTest
[ RUN      ] TcmallocDeathTest.NewArrayAndDelete

[WARNING] thirdparty/gtest-1.6.0/src/gtest-death-test.cc:789:: Death tests use 
fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
[       OK ] TcmallocDeathTest.NewArrayAndDelete (561 ms)
[ RUN      ] TcmallocDeathTest.NewAndFree

[WARNING] thirdparty/gtest-1.6.0/src/gtest-death-test.cc:789:: Death tests use 
fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
[       OK ] TcmallocDeathTest.NewAndFree (124 ms)
[ RUN      ] TcmallocDeathTest.Overflow

[WARNING] thirdparty/gtest-1.6.0/src/gtest-death-test.cc:789:: Death tests use 
fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
[       OK ] TcmallocDeathTest.Overflow (111 ms)
[ RUN      ] TcmallocDeathTest.Underflow

[WARNING] thirdparty/gtest-1.6.0/src/gtest-death-test.cc:789:: Death tests use 
fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
[       OK ] TcmallocDeathTest.Underflow (118 ms)
[----------] 4 tests from TcmallocDeathTest (914 ms total)

[----------] 3 tests from Tcmalloc
[ RUN      ] Tcmalloc.AllocAndFree
[       OK ] Tcmalloc.AllocAndFree (0 ms)
[ RUN      ] Tcmalloc.NewAndDelete
[       OK ] Tcmalloc.NewAndDelete (0 ms)
[ RUN      ] Tcmalloc.NewArrayAndDeleteArray
[       OK ] Tcmalloc.NewArrayAndDeleteArray (0 ms)
[----------] 3 tests from Tcmalloc (0 ms total)

[----------] Global test environment tear-down
[==========] 7 tests from 2 test cases ran. (915 ms total)
[  PASSED  ] 7 tests.
Thread finding failed with -1 errno=1
Could not find thread stacks. Will likely report false leak positives.
Check failed: regions_ != NULL: 
Aborted (core dumped)
Blade(info): thirdparty/perftools/tcmalloc_test finished : FAILED

Blade(info): Running thirdparty/glog/glog_test
WARNING: Perftools heap leak checker is active -- Performance may suffer
[==========] Running 2 tests from 2 test cases.
[----------] Global test environment set-up.
[----------] 1 test from GLogDeathTest
[ RUN      ] GLogDeathTest.Fatal

[WARNING] thirdparty/gtest-1.6.0/src/gtest-death-test.cc:789:: Death tests use 
fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
[       OK ] GLogDeathTest.Fatal (186 ms)
[----------] 1 test from GLogDeathTest (186 ms total)

[----------] 1 test from GLog
[ RUN      ] GLog.Test
E1228 23:22:16.043531  5885 thirdparty/glog/glog_test.cpp:12] ERROR
E1228 23:22:16.043531  5885 thirdparty/glog/glog_test.cpp:13] RAW: 
RAW_LOG(ERROR)
[       OK ] GLog.Test (0 ms)
[----------] 1 test from GLog (0 ms total)

[----------] Global test environment tear-down
[==========] 2 tests from 2 test cases ran. (186 ms total)
[  PASSED  ] 2 tests.
Thread finding failed with -1 errno=1
Could not find thread stacks. Will likely report false leak positives.
Check failed: regions_ != NULL: 
Aborted (core dumped)
Blade(info): thirdparty/glog/glog_test finished : FAILED

Blade(info): Running thirdparty/gtest/gtest_test
WARNING: Perftools heap leak checker is active -- Performance may suffer
Running main() from gtest_main.cc
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from GTest
[ RUN      ] GTest.Test
[       OK ] GTest.Test (0 ms)
[----------] 1 test from GTest (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (0 ms total)
[  PASSED  ] 1 test.
Thread finding failed with -1 errno=1
Could not find thread stacks. Will likely report false leak positives.
Check failed: regions_ != NULL: 
Aborted (core dumped)
Blade(info): thirdparty/gtest/gtest_test finished : FAILED

Blade(info): There are 3 tests scheduled to run by scheduler
Blade(info): ============= Testing Summary =============
Blade(info): Run 3 test targets
Blade(info): 3 tests failed:
thirdparty/perftools/tcmalloc_test, exit code: 134
thirdparty/glog/glog_test, exit code: 134
thirdparty/gtest/gtest_test, exit code: 134
Blade(info): 0 tests passed
Blade(info): 1 tests skipped when doing incremental test
Blade(info): to run all tests, please specify --full-test argument