Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (5)
to General by teroyk - 6 hrs, 22 mins ago -
Extra softwares in Sailfish using CLI, repositories, etc (118)
to SailfishOS by nieldk - 11 hrs, 36 mins ago -
Paths (0)
to Maemo 7 / Leste by teroyk - 1 day, 9 hrs ago - more...
 |
|
2010-05-31
, 09:58
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#2
|
There aren't any build instructions for your library.
The debian/rules files only has the instruction to copy your .c
file to the destination directory.
I don't know how other (if there any) Python/C packages are handled.
I would suggest you make a "real" debian package for your library.
(look for example at my profilesx package, how a simple project for a
control panel applet could look like).
And add your py-stuff to this package. I think python code can
be handled by the install instruction in the makefile like
icon image files, they just have to be copied somewhere,
right?
nicolai
The debian/rules files only has the instruction to copy your .c
file to the destination directory.
I don't know how other (if there any) Python/C packages are handled.
I would suggest you make a "real" debian package for your library.
(look for example at my profilesx package, how a simple project for a
control panel applet could look like).
And add your py-stuff to this package. I think python code can
be handled by the install instruction in the makefile like
icon image files, they just have to be copied somewhere,
right?
nicolai
| The Following User Says Thank You to nicolai For This Useful Post: | ||
 |
|
2010-05-31
, 11:28
|
|
Posts: 385 |
Thanked: 344 times |
Joined on Jan 2010
@ Israel
|
#3
|
Originally Posted by nicolai
I see.
There aren't any build instructions for your library.
The debian/rules files only has the instruction to copy your .c
file to the destination directory.
I don't know how other (if there any) Python/C packages are handled.
I would suggest you make a "real" debian package for your library.
(look for example at my profilesx package, how a simple project for a
control panel applet could look like).
And add your py-stuff to this package. I think python code can
be handled by the install instruction in the makefile like
icon image files, they just have to be copied somewhere,
right?
nicolai
Thank you!
Can you point me to the part of the deb file that specify that rule? I tried looking for it in your .deb but couldn't find it.
|
|
2010-05-31
, 11:41
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#4
|
Hi,
the debian/rules file simply calls "make" to clean, build or install
the components.
The important part is the makefile. How did you build the
callnotiry control panel applet previously?
the debian/rules file simply calls "make" to clean, build or install
the components.
The important part is the makefile. How did you build the
callnotiry control panel applet previously?
|
|
2010-05-31
, 12:08
|
|
Posts: 385 |
Thanked: 344 times |
Joined on Jan 2010
@ Israel
|
#5
|
Originally Posted by nicolai
I compiled it with esbox in scratchbox, but I can't manage to update the esbox libs to PR1.2, therefor I can't compile the c file to PR1.2 ...
Hi,
the debian/rules file simply calls "make" to clean, build or install
the components.
The important part is the makefile. How did you build the
callnotiry control panel applet previously?
So I'm pretty much stuck right now - I have a working python version of CallNotify and a .c file for the control panel plugin, but no way to compile it...
Any chance you can compile my .c to ARM target and provide me the output .so file?... So I can upload a working version until I'll get a handle of this packaging thingy?
|
|
2010-05-31
, 13:53
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#6
|
Don't know if this works. (this is the first
time I used madde to compile something).
Hope it works
nicolai
Last edited by nicolai; 2010-05-31 at 13:55.
time I used madde to compile something).
Hope it works
nicolai
Last edited by nicolai; 2010-05-31 at 13:55.
| The Following User Says Thank You to nicolai For This Useful Post: | ||
|
|
2010-05-31
, 17:53
|
|
Posts: 385 |
Thanked: 344 times |
Joined on Jan 2010
@ Israel
|
#7
|
Originally Posted by nicolai
Thanks! trying now...
Don't know if this works. (this is the first
time I used madde to compile something).
Hope it works
nicolai
|
|
2010-05-31
, 18:00
|
|
Posts: 385 |
Thanked: 344 times |
Joined on Jan 2010
@ Israel
|
#8
|
Originally Posted by omeriko9
Nope - it looks likes it depends on the old library libglib-2.0.so.0:
Thanks! trying now...
dpkg-shlibdeps: error: couldn't find library libglib-2.0.so.0 needed by debian/callnotify/usr/lib/hildon-control-panel/libcallnotify.so (ELF format: 'elf32-littlearm'; RPATH: '').
Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/callnotify.substvars debian/callnotify/usr/lib/hildon-control-panel/libcallnotify.so returned exit code 2
make: *** [binary-arch] Error 9
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
I've attached the latest source to this post.
Any ideas?