Hi Arndt
First things first, thank you very much for your prompt response.
I had seen sources at https://sourceforge.net/projects/synce/files/ dated
from May 2012, very old.
And the most recent ones at
https://launchpad.net/~synce/+archive/ubuntu/ppa/ with packages for Ubuntu
Xenial dated between August and October 2016.
I saw that they even take into account the change in the DHCP client, among
others. That's why I took it.
Thanks for the tip regarding the newest sources available.
I'm having a hard time understanding the organization of the many folders
and sources in /trunk
I want to build the following packages: libmimedir, librra, librtfcomp,
synce-core and synce-sync-engine.
I understand that they are the minimum packages necessary for a connection
with the devices.
In /trunk, the library libmimedir is not found, no longer needed?
I also don't see the sources to build the synce-core-engine binary, there
is a sync-engine folder but it doesn't seem complete, no Makefile,
autogen.sh, etc.
Another question, after executing the script (with autogen and make), I'm
already in a position to add Debian specific modifications under the debian
directory, and create the set of input files used for Debian package
building in quilt format?
As I said, my area is not package development but I am interested in
learning. I have many questions, sorry if they may seem trivial.
Thanks in advance
El jue, 3 nov 2022 a la(s) 20:05, Arndt Kaiser (arnd...@gmx.de) escribió:
> Hello Gustavo,
>
> it sounds like you are using very old sources or source packages. Many
> things have changed since then. As far as i remember the package with
> the name "python" was removed and replaced by "python2" and "python3"
> during the python3 transition.
>
> When you really are interested in compiling the old sources then the
> dependency "python" of the package should be changed to "python2"
> because the old sources contain scripts for python version 2.
>
> But i strongly recommend to use the newest available version of the core
> package available at www.sourceforge.net. During 2021 I modyfied all
> python scripts to use python3 and a lot of Bugfixing was done to the c
> sourcecode as well.
>
> The drawback is, that currently no build system for debian packages
> exists in the repository. This is up to you...
>
> To build the binary files, you can use something like this in a bash
> script:
>
> #####
> TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1
> SYNCE_CORE_PATH="${TMP_DIR}/synce-core"
>
> # Download sources from SourceForge
> svn export "https://svn.code.sf.net/p/synce/code/trunk/core";
> "${SYNCE_CORE_PATH}" || exit 1
> cd "${SYNCE_CORE_PATH}" || exit 1
>
> # Build sourcecode with non-root user
> export PATH="$PATH:/sbin"
> export CFLAGS="-O2"
> ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1
> make clean || exit 1
> make || exit 1
> echo "build successful"
> #####
>
> The following debian packages (bullseye) should be installed to compile
> the sources:
> libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool
> make g++
>
>
> Hope this helps.
>
>
> Cheers, Arndt
>
>
>
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
