summaryrefslogtreecommitdiff
path: root/libopie2/libopie2.pro
authormickeyl <mickeyl>2005-07-10 18:23:38 (UTC)
committer mickeyl <mickeyl>2005-07-10 18:23:38 (UTC)
commit71fc7a0b9722b1a9695049f2885d5247449fbd6c (patch) (unidiff)
tree4006dff6f7333e72156426b7740a5ea725accc3a /libopie2/libopie2.pro
parent779359497a582d510da0448f41a14e44db6b52af (diff)
downloadopie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.zip
opie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.tar.gz
opie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.tar.bz2
s/opieshower/opiebluez/, infrared better goes through opienet
there's the need of a connection abstraction library which bases on opienet and opiebluez in the future. It's for discussion if it makes sense in Opie 1.x
Diffstat (limited to 'libopie2/libopie2.pro') (more/less context) (ignore whitespace changes)
-rw-r--r--libopie2/libopie2.pro2
1 files changed, 1 insertions, 1 deletions
diff --git a/libopie2/libopie2.pro b/libopie2/libopie2.pro
index f131a9b..964caca 100644
--- a/libopie2/libopie2.pro
+++ b/libopie2/libopie2.pro
@@ -1,11 +1,11 @@
1TEMPLATE = subdirs 1TEMPLATE = subdirs
2unix:SUBDIRS = opiecore opiedb opiepim opieui opienet opiemm opiesecurity opieshower 2unix:SUBDIRS = opiecore opiedb opiepim opieui opienet opiemm opiesecurity opiebluez
3 3
4!contains( platform, x11 ) { 4!contains( platform, x11 ) {
5 message( Configuring libopie2 for build on Opie ) 5 message( Configuring libopie2 for build on Opie )
6 include( $(OPIEDIR)/include.pro ) 6 include( $(OPIEDIR)/include.pro )
7} 7}
8 8
9contains( platform, x11 ) { 9contains( platform, x11 ) {
10 message( Configuring libopie2 for build on Qt/X11 ) 10 message( Configuring libopie2 for build on Qt/X11 )
11} 11}