I tried
scons --verbose
scons -verbose
Seems both gave me the version information, not the verbose mode. I wish to look into some more details on how scons build my project. Is there a command line for this?
I know python support asian language, no problem
$ python
Python 2.7.13 (default, Dec 17 2016, 23:03:43)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> print '妳好'
妳好
I tried inside my SConscript
print "妳好".
scons prints some error:
SyntaxError: Non-ASCII character '\xe5' in file /home/abc/SConstruct on line 2, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
I wish to know if SCons supports asian languages in its print?
Thanks.
Q1: Does SCons support --verbose?
A1: No see the man page or use scons -h to see all supported flags
http://scons.org/doc/production/HTML/scons-man.html
Q2: Does SCons support foreign languages?
A2: You're questions might be better asked as "Does SCons support unicode?". In which case the answer is Not Really. But we're working on python 3 port which should
Related
Pandoc natively supports lua filter by its --lua-filter argument.
However, I am wondering however what version of lua is it using and whether it is possible to import lua modules such as luacom (which i believe relies on C code) into it.
This is part of my investigation to create a filter that reads excel worksheet and converts them to pandoc table.
It is generally possible to check the Lua version by running print(_VERSION). I.e., running this in your shell should work:
pandoc --lua-filter <(echo 'print(_VERSION)') <<< ''
Older pandoc versions could be compiled with any of Lua 5.1, Lua 5.2, Lua 5.3, or LuaJIT. However, maintaining compatibility was burdensome, so the maintainer of the HsLua package used by pandoc (i.e., I), stopped supporting older versions about a year ago. If you are using pandoc 2.3.1 or later, pandoc is guaranteed to contain Lua 5.3.x.
Loading pure Lua libraries will be no problem and should work just as with a plain Lua executable. The only problem can be that the default LUA_PATH set in pandoc differs from that used in other programs. This can happen if pandoc has not been compiled against the system-wide Lua version. LuaRocks can help there, just run eval "$(luarocks path)".
Same as with pure Lua libraries, C Lua libraries should just work if pandoc has been compiled as a non-static binary. However, non-Windows binaries provided on the pandoc website and on GitHub are static, and dynamic loading of C libraries will not work.
We maintain Alpine-based Docker images, pandoc/core and pandoc/latex, which are compiled against the system-wide Lua version. This can be a good option if your platform's package manager doesn't ship a recent pandoc version, can't use the statically compiled binary, and you don't want to compile pandoc yourself. If you'd like to see support for other base image like Ubuntu, just raise a ticket.
I ran clang++ -v testfile.cpp and found that many standard headers were missing from the directory C:\LLVM\lib\clang\3.9.0\include. I downloaded a pre-built binary of clang 3.9.0 for 32 bit windows from this link.
Can someone please help me sort out this mess and explain me why the standard libraries are missing in the pre-build version of clang? I've searched the web for hours to get the answer and solution to this problem but couldn't find one. Thanks in advance.
why the standard libraries are missing in the pre-build version of clang?
Your Windows binary download comprises only binary build tools
plus a handful of clang-specific headers because you are supposed
to use clang, on Windows, in lieu of another native compiler that provides your
standard library. Similarly if you install clang on Linux you'll build against
the GCC standard library by default.
Your internet search seemingly failed to lead you to Installing clang++ to compile and link on Windows, which
explains how to integrate clang with the mingw-w64 GCC standard library for 32- and/or 64-bit work
in the manner that clang for Windows expects and supports.
I already have part of a program running in Python 3 but I need OpenCV (or SimpleCV), for a robotic vehicle, but I haven't found any install commands that seem to work, other than for Python 2.7.
If it is compatible could you please include instructions (/links to) for installation of the module?
I am using Ubuntu 14.
Maybe a little late to answer, but it's actually supported on OpenCV version 3 (in alpha state nowadays). I have successfully managed to install it, on MacOS, but I guess it would be similar on Ubuntu.
Now you have separated options for python2 and python3 when using Cmake. So you'll have to set those to make it work. That's all I needed to set:
BUILD_opencv_python3
PYTHON3_LIBRARY
PYTHON3_INCLUDE_DIR
PYTHON3_INCLUDE_DIR2
PYTHON3_NUMPY_INCLUDE_DIRS
...
Here you can find more detailed description: Link
Luigolas is correct that OpenCV 3.0 supports Python 3.x bindings. It was in release candidate status since April and the production version was released on 4 June 2015. Unfortunately for some reason the downloadable installation program on the OpenCV site does not contain a Python 3.x-compatible cv2.pyd file.
OP asked about Ubuntu but for those requiring a Windows installer, use Christoph Gohlke's site, which maintains Windows binaries for many Python packages, including OpenCV 3.0 with Python 3.x bindings. Visit:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#opencv
To install, just download the 64-bit or 32-bit .whl file appropriate for your system, then run pip install [filename]. Then the instruction import cv2 should work in your Python 3.x interpreter.
How do I find out what DLLs an executable depends on?
On systems with the GNU development toolchain (gcc &c) I use ldd for that, but what about the clang systems, like, e.g., Mac OS X (which does not have ldd)?
On Mac OSX, you'd use otool -L instead of ldd. This works regardless of the compiler you used. Other operating systems may have yet other tools; e.g. on Windows you'd use Dependency Walker.
llvm-readelf ---needed-libs is the clang analogue of ldd. Here's is the official documentation
~/weechat $ llvm-readelf --needed-libs bin/weechat
NeededLibraries [
libc.so
libcurl.so
libdl.so
libgcrypt.so
libgnutls.so
libgpg-error.so
libiconv.so
libm.so
libncursesw.so.6
]
Decided to try out F# for the first time on my Mac (OSX 10.8, XCode 4.4). I downloaded Mono 3.0.3 and attempted to compile a simple "Hello World" program. It didn't go well:
$ cat Hello.fs
printfn "Hello, World!"
$ /Library/Frameworks/Mono.framework/Versions/3.0.3/bin/fsharpc Hello.fs
F# Compiler for F# 3.0 (Open Source Edition)
Freely distributed under the Apache 2.0 Open Source License
$ ./Hello.exe
zsh: exec format error: ./Hello.exe
$ file Hello.exe
Hello.exe: PE32 executable for MS Windows (console) Intel 80386 32-bit Mono/.Net assembly
I looked through the output of fsharpc --help to see if there was an obvious flag for producing the correct type of binary, but nothing seemed particularly helpful. I'm assuming that there's something really obvious I need to do to enable this, but I can't seem to figure it out.
I just realized that I was supposed to do mono Hello.exe. I'll leave this around in case somebody else doesn't read the Mono documentation before trying to compile some code ;)