building on lucid
Sebastian Kuzminsky
http://git.highlab.com/?p=opencamlib.git/.git;a=shortlog;h=refs/heads/build-on-lucid
That branch makes a couple of small changes to the build system so it
can build on Lucid. I also tested it on Precise and it builds there too.
There is still some at least one strange hickup, when I build a package
the resulting package is named "opencamlib-..-Linux.deb", which seems
like it's missing something... The Git version perhaps? In any case,
that's not a normal-looking debian version number... I'll look into it
more. The funny-named package does install.
What should I do to test it? Which of the scripts in the scripts/
directory are most useful?
--
Sebastian Kuzminsky
Sebastian Kuzminsky
> Hi Anders, please consider pulling the "build-on-lucid" branch from here:
>
> http://git.highlab.com/?p=opencamlib.git/.git;a=shortlog;h=refs/heads/build-on-lucid
>
Oops, that's the gitweb interface. The real pull url is:
<http://git.highlab.com/git/opencamlib.git>
--
Sebastian Kuzminsky
Anders Wallin
> <http://git.highlab.com/git/opencamlib.git>
"git pull" from this URL gives your master branch. I don't know what
the URL for your "build-on-lucid" would be ??
AW
Sebastian Kuzminsky
Sorry, I forgot to put the branch name in the pull request. Let me try
a third time...
Oh hey look, there's a "git request-pull" command! Hmm... Ok, here's
the output of "git request-pull origin/master
http://git.highlab.com/git/opencamlib.git build-on-lucid":
The following changes since commit 8a7b3873b3d360d2d617f3c5c4f99bbbdbf08862:
Anders Wallin (1):
make the py-libs install correctly
are available in the git repository at:
http://git.highlab.com/git/opencamlib.git build-on-lucid
Sebastian Kuzminsky (3):
fix a copy/paste bug in an error message
look for git "by hand" if Cmake can't find it
strip whitespace from git describe
src/version_string.cmake | 20 +++++++++++++++++++-
1 files changed, 19 insertions(+), 1 deletions(-)
So try "git pull http://git.highlab.com/git/opencamlib.git build-on-lucid"
--
Sebastian Kuzminsky
Anders Wallin
> http://git.highlab.com/?p=opencamlib.git/.git;a=shortlog;h=refs/heads/build-on-lucid
Thanks. Merged that now.
> That branch makes a couple of small changes to the build system so it can
> build on Lucid. I also tested it on Precise and it builds there too.
The same changes/problems probably occur for truetypetracer and
openvoronoi also? Although the source-packages for these do build
successfully on Launchpad for Lucid and the other ubuntu versions.
> There is still some at least one strange hickup, when I build a package the
> resulting package is named "opencamlib-..-Linux.deb", which seems like it's
> missing something... The Git version perhaps? In any case, that's not a
> normal-looking debian version number... I'll look into it more. The
> funny-named package does install.
If you have git, and a git-repo then the version comes from "git
describe --tags". Since I did not want to include the whole git-repo
into the source-package I upload to Launchpad instead the results of
"git describe --tags" is written to a file (from which the version is
later read).
on my system the only quirk that remains is that "make package" (a
target that should build a binary deb-package, generated by CPack),
doesn't get the architecture right. The package ends up named
"...Linux.deb" when I think it should be "...amd64.deb"
I am building the source-packages for launchpad with "make spackage" a
target that runs DebSourcePPA.cmake
> What should I do to test it? Which of the scripts in the scripts/ directory
> are most useful?
Most of the scripts I use for development/testing are in
https://github.com/aewallin/opencamlib/tree/master/scripts and they
use VTK and the VTK python-bindings for visualization. None of the
scripts are installed or come with the debian source-package..
So far there's only one script that produces G-code directly:
https://github.com/aewallin/linuxcnc-scripts/blob/master/stl2parallel_finish_zig.py
(there's a screenshot in the gallery)
Anders