>PNG menu icons are automatically extracted from .ico
Good!
> New modifications in Makefile (better clean target)
Why is it necessary to configure before clean-up?
> During deb packaging, I can see these warnings:
`wx-config` links against all available libraries by default. So unless one
specifies all required libraries manually (which is not a good idea with
regards to long term maintenance) I see no way to avoid these warnings.
Additionally: Using `wx-config` for compiling and linking is the official way
to do this.
Modifications to build .deb package
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
- Posts: 20
- Joined: 22 Jun 2002
> > New modifications in Makefile (better clean target)
> Why is it necessary to configure before clean-up?
You're right, here is much better way to be able to call "clean" target even
if ossp_uuid configure has never been called.
Replace "cd shared/ossp_uuid && make clean" by
if ; then cd shared/ossp_uuid && make clean ; fi
> > During deb packaging, I can see these warnings:
Warnings are warnings, I will just ignore them.
For the future inclusion in Ubuntu, it would be good the see a license header
in each text file.
Do you know what is the license of your images ?
> Why is it necessary to configure before clean-up?
You're right, here is much better way to be able to call "clean" target even
if ossp_uuid configure has never been called.
Replace "cd shared/ossp_uuid && make clean" by
if ; then cd shared/ossp_uuid && make clean ; fi
> > During deb packaging, I can see these warnings:
Warnings are warnings, I will just ignore them.
For the future inclusion in Ubuntu, it would be good the see a license header
in each text file.
Do you know what is the license of your images ?
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
> if ; then cd shared/ossp_uuid && make clean ; fi
Why not simply "cd shared/ossp_uuid && make clean". There is nothing that can
go wrong with it, is there?
> For the future inclusion in Ubuntu, it would be good the see a license
header in each text file.
> Do you know what is the license of your images?
The images have various licenses, but all are fine with Open Source usage, I
checked this explicitly.
And as for the text files, I'm not sure if I want to cluster them with this
redundant license headers.
I don't think it is really legally required as the license becomes obvious at
a number of other places.
Why not simply "cd shared/ossp_uuid && make clean". There is nothing that can
go wrong with it, is there?
> For the future inclusion in Ubuntu, it would be good the see a license
header in each text file.
> Do you know what is the license of your images?
The images have various licenses, but all are fine with Open Source usage, I
checked this explicitly.
And as for the text files, I'm not sure if I want to cluster them with this
redundant license headers.
I don't think it is really legally required as the license becomes obvious at
a number of other places.
- Posts: 20
- Joined: 22 Jun 2002
> There is nothing that can go wrong with it, is there?
Yes, if configure has never been called, Makefile doesn't exist and "make
clean" fails.
Source deb packaging process begins with "make clean" which calls "cd
shared/ossp_uuid && make clean". As ossp_uuid Makefile doesn't exist, it
fails.
I don't know If there is a better way to handle this issue.
> And as for the text files, I'm not sure if I want to cluster
> them with this redundant license headers.
> I don't think it is really legally required as the license
> becomes obvious at a number of other places.
There is not need to do that quickly, but according to
https://wiki.ubuntu.com/PackagingGuide/Complete%23Copyright
"For all files it must be clear under which license they fall. Source code
files should usually have a short comment at the top which points out the
license."
Your IDE could managed that for you seamlessly.
I did a "grep -ir copyright *" on FFS, and, waoh, there are many external
files, with their own license.
I will have to add them to [404, Invalid URL: http://bazaar.launchpad.net/%7Edlecan/%2Bjunk/ffs-devel/annotate/head%3A/debian/copyright] if they are not GPLv3.
Yes, if configure has never been called, Makefile doesn't exist and "make
clean" fails.
Source deb packaging process begins with "make clean" which calls "cd
shared/ossp_uuid && make clean". As ossp_uuid Makefile doesn't exist, it
fails.
I don't know If there is a better way to handle this issue.
> And as for the text files, I'm not sure if I want to cluster
> them with this redundant license headers.
> I don't think it is really legally required as the license
> becomes obvious at a number of other places.
There is not need to do that quickly, but according to
https://wiki.ubuntu.com/PackagingGuide/Complete%23Copyright
"For all files it must be clear under which license they fall. Source code
files should usually have a short comment at the top which points out the
license."
Your IDE could managed that for you seamlessly.
I did a "grep -ir copyright *" on FFS, and, waoh, there are many external
files, with their own license.
I will have to add them to [404, Invalid URL: http://bazaar.launchpad.net/%7Edlecan/%2Bjunk/ffs-devel/annotate/head%3A/debian/copyright] if they are not GPLv3.
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
> Yes, if configure has never been called, Makefile doesn't exist and "make
clean" fails.
You're right, in this case the existence check is okay.
> I did a "grep -ir copyright *" on FFS, and, waoh, there are many external
files, with their own license.
> I will have to add them to [404, Invalid URL: http://bazaar.launchpad.net/%7Edlecan/%2Bjunk/ffs-devel/annotate/head%3A/debian/copyright] if they are not GPLv3.
The external packages I use are:
wxWidgets (http://www.wxwidgets.org)
-> http://www.wxwidgets.org/about/newlicen.htm
Boost (http://www.boost.org))
-> http://www.boost.org/users/license.html
Inotify (http://inotify.aiken.cz/?section=inotify-cxx&page=about&lang=en)
-> GNU GPL version 2 or GNU LGPL version 2.1 or a X11-style license
Loki (https://sourceforge.net/projects/loki-lib/)
-> MIT License
Ossp UUID
(http://www.ossp.org/pkg/lib/uuid/))
-> http://www.ossp.org/doc/license.html
TinyXml (https://sourceforge.net/projects/tinyxml/)
-> zlib/libpng License
clean" fails.
You're right, in this case the existence check is okay.
> I did a "grep -ir copyright *" on FFS, and, waoh, there are many external
files, with their own license.
> I will have to add them to [404, Invalid URL: http://bazaar.launchpad.net/%7Edlecan/%2Bjunk/ffs-devel/annotate/head%3A/debian/copyright] if they are not GPLv3.
The external packages I use are:
wxWidgets (http://www.wxwidgets.org)
-> http://www.wxwidgets.org/about/newlicen.htm
Boost (http://www.boost.org))
-> http://www.boost.org/users/license.html
Inotify (http://inotify.aiken.cz/?section=inotify-cxx&page=about&lang=en)
-> GNU GPL version 2 or GNU LGPL version 2.1 or a X11-style license
Loki (https://sourceforge.net/projects/loki-lib/)
-> MIT License
Ossp UUID
(http://www.ossp.org/pkg/lib/uuid/))
-> http://www.ossp.org/doc/license.html
TinyXml (https://sourceforge.net/projects/tinyxml/)
-> zlib/libpng License
- Posts: 20
- Joined: 22 Jun 2002
Thank you for this list of licenses.