17 Sep
2011
17 Sep
'11
9:47 a.m.
Hi. I'm not sure if I'm writing the right mailing list so sorry if it isn't
so. Also sorry for my not very good english...
Is there any special need for using "add_subdirectory " insted of
"tde_conditional_add_subdirectory" for kcontrol, kdmlib etc?
I think it's better to include all subdirectories via tde's function...
isn't it?
17 Sep
17 Sep
9:54 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
On Saturday 17 September 2011 12:47:20 Fat-Zer wrote:
Hi. I'm not sure if I'm writing the right
mailing list so sorry if it isn't
so. Also sorry for my not very good english...
Is there any special need for using "add_subdirectory " insted of
"tde_conditional_add_subdirectory" for kcontrol, kdmlib etc?
I'm not sure that I undestand your problem. The purpose
of "tde_conditional_add_subdirectory" is to include a directory only if the
condition is true (as the name suggests).
I think it's better to include all subdirectories
via tde's function...
isn't it?
For what reason?
--
Serghei
11:01 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
2011/9/17 Serghei Amelian <serghei(a)thel.ro>
On Saturday 17 September 2011 12:47:20 Fat-Zer wrote:
Thanks for quick reply...
I'll start from the beginning: I'm writing live ebuilds for trinity now and
run into that there are same files are in each package from kdebase.
General reason: i think the system should compile only that you asked for...
Patch in the attach will describe better what i'm talking about...
ps: thanks for your repository on the githup (i wrote directly to you
several months ago)... it helped me to start...
Hi. I'm not sure if I'm writing the right
mailing list so sorry if it
isn't
so. Also sorry for my not very good english...
Is there any special need for using "add_subdirectory " insted of
"tde_conditional_add_subdirectory" for kcontrol, kdmlib etc?
I'm not sure that I undestand your problem. The purpose
of "tde_conditional_add_subdirectory" is to include a directory only if the
condition is true (as the name suggests).
I think it's better to include all
subdirectories via tde's function...
isn't it?
For what reason?
--
Serghei
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
11:30 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
On Saturday 17 September 2011 14:01:01 Fat-Zer wrote:
2011/9/17 Serghei Amelian <serghei(a)thel.ro>
Good news, unfortunately my spare time became very little and I can't be
productive as before.
On Saturday 17 September 2011 12:47:20 Fat-Zer
wrote:
Thanks for quick reply...
I'll start from the beginning: I'm writing live ebuilds for trinity now and
run into that there are same files are in each package from kdebase. Hi. I'm not sure if I'm writing the right
mailing list so sorry if it
isn't
so. Also sorry for my not very good english...
Is there any special need for using "add_subdirectory " insted of
"tde_conditional_add_subdirectory" for kcontrol, kdmlib etc?
I'm not sure that I undestand your problem. The purpose
of "tde_conditional_add_subdirectory" is to include a directory only if
the condition is true (as the name suggests).
I think it's better to include all
subdirectories via tde's function...
isn't it?
For what reason? General reason: i think the system should compile only
that you asked
for... Patch in the attach will describe better what i'm talking about...
Actually, I did this everywhere was possible. For example, if you looking into
kcontrol/CMakeLists.txt you will notice that "background" directory is needed
for kdesktop and kdm either.
ps: thanks for your repository on the githup (i wrote
directly to you
several months ago)... it helped me to start...
Welcome.
--
Serghei
12:40 p.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
2011/9/17 Serghei Amelian <serghei(a)thel.ro>
On Saturday 17 September 2011 14:01:01 Fat-Zer wrote:
I'll try to
compile everything in kdebase with that patch and report the
results...
Thanks for quick reply...
I'll start from the beginning: I'm writing live ebuilds for trinity now
and
run into that there are same files are in each
package from kdebase.
Good news, unfortunately my spare time became very little and I can't be
productive as before.
General reason: i think the system should compile
only that you asked
for... Patch in the attach will describe better what i'm talking about...
Actually, I did this everywhere was possible. For example, if you looking
into
kcontrol/CMakeLists.txt you will notice that "background" directory is
needed
for kdesktop and kdm either.
I'm sure it will work at least for krootbacking and tsak. ps: thanks for
your repository on the githup (i wrote directly to you
several months ago)... it helped me to start...
Welcome.
--
Serghei
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
5:56 p.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
2011/9/17 Fat-Zer <fatzer2(a)gmail.com>
I'm sure it will work at least for krootbacking and tsak.
I'll try to compile everything in kdebase with that patch and report the
results...
ok... I watched thorough kdmlib's CMakeList.txt and it's really well-done.
except latest patches... what about moving kdmtsac to kdm directory? I think
it's not logical to keep binary with libs... isn't it?
or what about merging it with mainline kdm and add another cmake flag to
determine what to build with tsoc support or without?
6:07 p.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
On Saturday 17 September 2011 20:56:20 Fat-Zer wrote:
2011/9/17 Fat-Zer <fatzer2(a)gmail.com>
Not sure, Tim should know better.
--
Serghei
I'm sure it will work at least for
krootbacking and tsak.
I'll try to compile everything in kdebase with that patch and report the
results...
ok... I watched thorough kdmlib's CMakeList.txt and it's really
well-done.
except latest patches... what about moving kdmtsac to kdm directory? I
think it's not logical to keep binary with libs... isn't it?
or what about merging it with mainline kdm and add another cmake flag to
determine what to build with tsoc support or without?
18 Sep
18 Sep
11:50 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
ok... for clearence. what kdmtsac is? what is it need for?
10:29 p.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
what about this?
21 Sep
21 Sep
12:50 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
fix
3:05 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
I structured related problems. Tell me if i'm wrong.
1. Move kdmtsac to kdm dir
Arguments: it's binary and it's place is not in kdmLIB directory. And it's
used only by kdm.
2. move tsac to kdm too
Arguments: The same + it's too small for separate module and hightly
integrated with kdm
3. Chose a good flag for tsac support by kdm e.g.: WITH_TSAC
4. Move krootbacking to kscreensaver and add flag WITH_KROOTBACKING
Arguments: it's too small, highly integrated with kscreensaver by logic and
nobody else using it.
previous patch was just a temporary workaround...
3:59 a.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
I structured related problems. Tell me if i'm
wrong.
1. Move kdmtsac to kdm dir
Arguments: it's binary and it's place is not in kdmLIB directory. And it's
used only by kdm.
Also used by kdesktop_lock.
2. move tsac to kdm too
Arguments: The same + it's too small for separate module and hightly
integrated with kdm
Not at all integrated with KDM actually--it is the Secure
Attention Key
daemon that can be accessed and used by any other program with root
access.
3. Chose a good flag for tsac support by kdm e.g.:
WITH_TSAC
4. Move krootbacking to kscreensaver and add flag WITH_KROOTBACKING
Arguments: it's too small, highly integrated with kscreensaver by logic
and
nobody else using it.
It is not actually integrated with kscreensaver--kscreensaver
needs and
calls it, but any other application could do the same. All this program
does is write out a current snapshot of the Trinity desktop wallpaper to a
.png file in the /tmp directory.
previous patch was just a temporary workaround...
23 Oct
23 Oct
10:22 p.m.
New subject: [trinity-devel] [cmake][kdbase] necessity of add_subdirectory
new fixes becose of adding tqt3integration
4578
days inactive
4614
days old
14 comments
3 participants
participants (3)
-
Fat-Zer -
Serghei Amelian -
Timothy Pearson