On Wed, 2002-10-02 at 12:58, John Batistic wrote:
> On Tue, 2002-10-01 at 22:58, Colin Watson wrote:
> > On Tue, Oct 01, 2002 at 10:51:12PM +1200, John Batistic wrote:
> > > On Tue, 2002-10-01 at 21:42, Colin Watson wrote:
> > > > Keep it simple and realize that this level of 'make' use is not all
LIBS = -lqt -lkdecore
works for me.
On Tuesday 01 October 2002 03:51 am, John Batistic wrote:
> On Tue, 2002-10-01 at 21:42, Colin Watson wrote:
> > On Tue, Oct 01, 2002 at 09:31:10PM +1200, John Batistic wrote:
> > > On Tue, 2002-10-01 at 21:06, Colin Watson wrote:
> > > > On Tue, Oct 01, 2002
On Tue, Oct 01, 2002 at 10:51:12PM +1200, John Batistic wrote:
> On Tue, 2002-10-01 at 21:42, Colin Watson wrote:
> > Keep it simple and realize that this level of 'make' use is not all that
> > magic. '-I$(INCLUDES)' doesn't work because it expands to
> > '-I-I/usr/share/qt/include -I/etc/kde2/in
On Tue, 2002-10-01 at 21:42, Colin Watson wrote:
> On Tue, Oct 01, 2002 at 09:31:10PM +1200, John Batistic wrote:
> > On Tue, 2002-10-01 at 21:06, Colin Watson wrote:
> > > On Tue, Oct 01, 2002 at 08:54:34PM +1200, John Batistic wrote:
> > > > INCLUDES= -I/usr/share/qt/include -I/etc/kde2/include
On Tuesday 01 October 2002 02:54 am, John Batistic wrote:
> INCLUDES= -I/usr/share/qt/include -I/etc/kde2/include
Are you absolutely positive that the qt includes are in
/usr/share/qt/include??
On my system, I have them in /usr/include/qt:
jas@golden:~$ locate qlabel.h
/usr/include/qt/qlabel.h
On Tue, Oct 01, 2002 at 09:31:10PM +1200, John Batistic wrote:
> On Tue, 2002-10-01 at 21:06, Colin Watson wrote:
> > On Tue, Oct 01, 2002 at 08:54:34PM +1200, John Batistic wrote:
> > > INCLUDES= -I/usr/share/qt/include -I/etc/kde2/include
> > > CFLAGS= -pipe -02 -fno-strength-reduce
> > > LFLAGS
On Tue, 2002-10-01 at 21:06, Colin Watson wrote:
> On Tue, Oct 01, 2002 at 08:54:34PM +1200, John Batistic wrote:
> > INCLUDES= -I/usr/share/qt/include -I/etc/kde2/include
> > CFLAGS= -pipe -02 -fno-strength-reduce
> > LFLAGS= -L/usr/share/qt/lib/ -L/usr/lib/kde2/lib -L/usr/X11R6/lib
> > LIBS= -lq
On Tue, Oct 01, 2002 at 08:54:34PM +1200, John Batistic wrote:
> INCLUDES= -I/usr/share/qt/include -I/etc/kde2/include
> CFLAGS= -pipe -02 -fno-strength-reduce
> LFLAGS= -L/usr/share/qt/lib/ -L/usr/lib/kde2/lib -L/usr/X11R6/lib
> LIBS= -lqt -lX11 -ltext
> CC=g++
>
> helloworld: helloworld.o
>
On Tue, 2002-10-01 at 14:54, Sean 'Shaleh' Perry wrote:
> On Monday 30 September 2002 18:26, John Batistic wrote:
> > >
> > > You do not state so let's start at the beginning.
> > >
> > > Do you have the -dev version of the kdelibs as well as qt installed?
> > > Rather than depend on environment
Craig Dickson <[EMAIL PROTECTED]> writes:
> Brian Nelson wrote:
>
>> Tom Cook <[EMAIL PROTECTED]> writes:
>>
>> > No, it's not worth it. I was just looking at the g++ man page that
>> > lists .cc and .cxx but not .cpp.
>>
>> Huh? I see:
>>
>> C++ source files use one of the suffixes `.C',
On 0, Brian Nelson <[EMAIL PROTECTED]> wrote:
> Tom Cook <[EMAIL PROTECTED]> writes:
>
> > On 0, Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
> >> On Monday 30 September 2002 19:04, Tom Cook wrote:
> >> > #include
> >> > #include
> >> > #include
> >> >
> >> > then you should be able to com
Brian Nelson wrote:
> Tom Cook <[EMAIL PROTECTED]> writes:
>
> > No, it's not worth it. I was just looking at the g++ man page that
> > lists .cc and .cxx but not .cpp.
>
> Huh? I see:
>
> C++ source files use one of the suffixes `.C', `.cc', `.cxx', `.cpp',
> or `.c++'; preprocessed C++
Tom Cook <[EMAIL PROTECTED]> writes:
> On 0, Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
>> On Monday 30 September 2002 19:04, Tom Cook wrote:
>> > #include
>> > #include
>> > #include
>> >
>> > then you should be able to compile with:
>> >
>> > g++ -c -o helloworld.o helloworld.cpp
>> >
>
On 0, Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
> On Monday 30 September 2002 19:04, Tom Cook wrote:
> > #include
> > #include
> > #include
> >
> > then you should be able to compile with:
> >
> > g++ -c -o helloworld.o helloworld.cpp
> >
> > Note also that the usual (proper?) way of nami
On Monday 30 September 2002 19:04, Tom Cook wrote:
> #include
> #include
> #include
>
> then you should be able to compile with:
>
> g++ -c -o helloworld.o helloworld.cpp
>
> Note also that the usual (proper?) way of naming C++ source is *.cc or
> *.cxx, not *.cpp like M$ do.
>
> Tom
actually
On 0, John Batistic <[EMAIL PROTECTED]> wrote:
> I am unable to compile the KDE2 helloworld.cpp example
>
> error message from make:
>
> g++-c -o helloworld.o helloworld.cpp
> helloworld.cpp:2: qapplication.h: No such file or directory
> helloworld.cpp:3
On 0, Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
> On Monday 30 September 2002 16:55, John Batistic wrote:
> > I am unable to compile the KDE2 helloworld.cpp example
> >
> > error message from make:
> >
> > g++-c -o helloworld.o hellow
On Monday 30 September 2002 16:55, John Batistic wrote:
> I am unable to compile the KDE2 helloworld.cpp example
>
> error message from make:
>
> g++-c -o helloworld.o helloworld.cpp
> helloworld.cpp:2: qapplication.h: No such file or directory
> helloworld.cpp:3: qlab
I am unable to compile the KDE2 helloworld.cpp example
error message from make:
g++-c -o helloworld.o helloworld.cpp
helloworld.cpp:2: qapplication.h: No such file or directory
helloworld.cpp:3: qlabel.h: No such file or directory
helloworld.cpp:4: qstring.h: No such file or directory
make
19 matches
Mail list logo
