Search Results

Search found 6 results on 1 pages for 'buildsystem'.

Page 1/1 | 1 

• Building a Debian package with two buildsystem

  - by queueoverflow

  I have a package that needs to be build with both a regular makefile and a setup.py. The thing is that the Debian packaging magic that is invoked via debuild would recognize a makefile and do the right make make install DESTDIR=??? thing and get it working right. When I only have a setup.py sitting there and have dh $@ --with python3 --buildsystem pybuild in debian/rules, it will correctly install the Python module with python3 setup.py build python3 setup.py install --install-layout deb --root=??? ??? I do not know all those flags. And I think that I do not need to. I just want the makefile magic to happen, and then the setup.py magic. How can I tell debuild to do both? When I do the following in debian/rules %: dh $@ dh $@ --with python3 --buildsystem pybuild it will only put the first one into the resulting package. I tried to delete the debhelper.log between those, but that did not change much.

  Read the article

• What are the hidden features of Maven2?

  - by Xymor

  What are the hidden features of Maven2?

  Read the article

• Licensing my own dh_* scripts

  - by avnik

  I wrote little helper script, for my own buildsystem. This script uses debhelper's Dh_lib to inject pre/post install fragments. use strict; use Debian::Debhelper::Dh_Lib; foreach my $package (@{$dh{DOPACKAGES}}) { autoscript($package, "postinst", "postinst-rock2deb"); autoscript($package, "postrm", "postrm-rock2deb"); } Should it be GPL'ed, because it use GPL'ed Dh_lib, or it uncopyrightable, because no other way to do it? Other scripts in my buildsystem are MIT/X licensed, and I prefer to stay with MIT/X when possible. (question moved from stackoverflow as suggested by few SG members)

  Read the article

• Export NFS path containing "-" (dash)

  - by qdot

  I'm in a bit of a pinch with NFS exports file. Specifically, I can't find a way to export a directory containing "-" in the path name. Manual (exports(5)) states: Also, each line may have one or more specifications for default options after the path name, in the form of a dash ("-") followed by an option list. The option list is used for all subsequent exports on that line only. It then states: If an export name contains spaces it should be quoted using double quotes. You can also specify spaces or other unusual character in the export name using a backslash followed by the character code as three octal digits. Unfortunately, that is not the case. Specifically, if the pathname contains "-", either verbatim, or with \055 or is enclosed in double quotes, it still refers to the name without "-" Any ideas? I have a large number of directories, all of the form /vol/buildsystem-s3c2440 /vol/buildsystem-tao3530 and I'd prefer to have them all available as nfs exports. Short of replacing the "-" with "_" everywhere in the scripts, can it be done with "-" ?

  Read the article

• C++11 support in GNU automake

  - by sorush-r

  I'm trying to port buildsystem of my project to GNU autotools. The code need to be compiled with -std=c++11 or -std=c++0x flag. I want my configure script to check if compiler supports C++11 or not. I tried adding AX_CHECK_COMPILE_FLAG([-std=c++0x], [CXXFLAGS="$CXXFLAGS -std=c++0x"]) to configure.ac file but configure fails with this error: ... ./configure: line 2732: syntax error near unexpected token `-std=c++0x,' ./configure: line 2732: `AX_CHECK_COMPILE_FLAG(-std=c++0x, CXXFLAGS="$CXXFLAGS -std=c++0x")'

  Read the article

• Best C# bindings for Qt?

  - by Stefan Monov

  I've written a game in C# with SDL.NET and OpenGL. I want to add a menu to it, for which I need Qt. What bindings do you recommend for Qt in C#? Qyoto? qt4dotnet? other? Requirements: fast should just work and be polished - i.e. no weird problems at every step integration with the buildsystem, uic, resources, etc, should work well

  Read the article

1