| author | mickeyl <mickeyl> | 2005-07-10 18:23:38 (UTC) |
|---|---|---|
| committer | mickeyl <mickeyl> | 2005-07-10 18:23:38 (UTC) |
| commit | 71fc7a0b9722b1a9695049f2885d5247449fbd6c (patch) (side-by-side diff) | |
| tree | 4006dff6f7333e72156426b7740a5ea725accc3a /libopie2/libopie2.pro | |
| parent | 779359497a582d510da0448f41a14e44db6b52af (diff) | |
| download | opie-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
| -rw-r--r-- | libopie2/libopie2.pro | 2 |
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 @@ TEMPLATE = subdirs -unix:SUBDIRS = opiecore opiedb opiepim opieui opienet opiemm opiesecurity opieshower +unix:SUBDIRS = opiecore opiedb opiepim opieui opienet opiemm opiesecurity opiebluez !contains( platform, x11 ) { message( Configuring libopie2 for build on Opie ) include( $(OPIEDIR)/include.pro ) } contains( platform, x11 ) { message( Configuring libopie2 for build on Qt/X11 ) } |