Issue 14 in google-js-test: Simplify the build process to work on Windows, Mac, and Linux

23 views
Skip to first unread message

google-...@googlecode.com

unread,
Oct 6, 2011, 7:30:37 AM10/6/11
to google-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 14 by gusver...@gmail.com: Simplify the build process to work on
Windows, Mac, and Linux
http://code.google.com/p/google-js-test/issues/detail?id=14

I would like to be able to easily build and run this tool on any of these
OSes.

Perhaps a GYP or SCons based solution could be implemented.

Thoughts?

google-...@googlecode.com

unread,
Oct 6, 2011, 6:06:41 PM10/6/11
to google-...@googlegroups.com
Updates:
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

Comment #1 on issue 14 by jaco...@google.com: Simplify the build process to

OS X: This is already pretty easy if you use the excellent homebrew package
manager. (See the Installing wiki page for details.) Have you tried this?

Linux: As far as I'm aware, this already works. It's true that you have to
install a bunch of prerequisites, which is kind of a pain. Better would be
to
have a package that works with apt-get, but the project lacks someone with
the
expertise to make that happen. (Let me know if you're interested.) I don't
think SCons would help here.

Windows: This is a much bigger challenge. If there's enough demand, it could
probably be done.

google-...@googlecode.com

unread,
Oct 12, 2011, 7:58:57 AM10/12/11
to google-...@googlegroups.com

Comment #2 on issue 14 by dev...@gmail.com: Simplify the build process to

please document which version of required libraries are needed.

to compile it under ubuntu, while the make && make install dance is
standard enough for me,
the apt version of protobufcompiler 2.0.3 raises "error regenerate this
file with a newer version of protoc." and should be avoided.
Instead manually install protubuf 2.4 under /usr/local/lib, which at first
raises "error while loading shared libraries: libprotobuf.so.7: cannot open
shared object file: No such file or directory",
then fix it with ./configure --prefix=/usr and finally install the missing
libxml++2.6-dev with apt.

while the resulting tester is damn fast and handy, that misconfiguration of
protobuf was quite hard to solve and can limit drastically the audience of
such pretty cool tool.

google-...@googlecode.com

unread,
Oct 12, 2011, 8:14:51 PM10/12/11
to google-...@googlegroups.com

Comment #3 on issue 14 by jaco...@google.com: Simplify the build process to

Could you try removing any versions of protobuf that you installed, then
install again with this command,

sudo apt-get install libprotobuf-dev

then try building gjstest again? This worked for me without trouble on
Ubuntu 11.04.

google-...@googlecode.com

unread,
Aug 1, 2013, 11:42:20 PM8/1/13
to google-...@googlegroups.com

Comment #4 on issue 14 by ja...@wildlemur.com: Simplify the build process
Just wanted to share the steps I use to get google-js-test running on
Ubuntu 12.10. I haven't been able to get it working in newer releases, so
I typically do JavaScript development in a virtual machine with this
setup...

Install prerequesites:

$ sudo apt-get install libgoogle-glog-dev
$ sudo apt-get install libprotobuf-dev
$ sudo apt-get install libxml2-dev
$ sudo apt-get install protobuf-compiler
$ sudo apt-get install libgflags-dev
$ sudo apt-get install libv8-dev

# For re2
$ cd /tmp
$ hg clone https://re2.googlecode.com/hg re2
$ cd re2
$ make test
$ sudo make install
$ make testinstall

# It may be necessary to refresh the shared library cache now
$ sudo ldconfig

Install google-js-test:

$ cd /tmp
$ git clone https://code.google.com/p/google-js-test/
$ cd google-js-test
# Checkout the latest release tag
$ git checkout release-1.0.8
$ make
$ sudo make install

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages