Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 1999-07

Useless Status Feedback

6 messages · 6 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Brad Campbell
to Michael A. Hess: I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the code from the…

G'day All

Just tried the latest from the CVS..
After building lazarus with a
ppc386 -Fu lcl lazarus
Worked like a charm....
Shane, the new Tcanvas stuff looks very cool.......

Keep on plugging....
I'm still working my way thru Developing Linux Apps in Gtk+/Gdk.. I hope to reach a useful state sometime this millenium... :p)

BTW :
Can anyone tell me what the -XX compiler switch does? It's the only way I can get my programs to smartlink... And it appears to be undocumented....

Cheers All.....

Brad....

"Where do YOU want Microsoft to go today"
"Why pay for a broken OS, when you can get one that works for free ?"

/"\
\ /
X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
/ \

Reply by email

Michael A. Hess

I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the code from the main directory, all that is blown away. None of the code is there dude!!!!!!!!

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Curtis White
to Michael Van Canneyt: I have fixed this; do a 'cvs update -d lazarus' Cliff; it seems that you made a NEW…

I just finished making the initial working version of the TNotebook component. It needs more work, but I now have it working and want to commit it to CVS. But when I tried to commit it, CVS told me I don't have permission to do that. So how do I get permission to commit my code to CVS?

I want to get it in there before someone changes gtkint again and I have to merge my changes back in to it.

Curtis

On 26-Jul-99 Michael Van Canneyt wrote 34 lines
On Sun, 25 Jul 1999, Michael A. Hess wrote: > I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the > code from the main directory, all that is blown away. None of the code > is there dude!!!!!!!! I have fixed this; do a 'cvs update -d lazarus' Cliff; it seems that you made a NEW repository, and all lcl stuff was placed there. I have moved the code to the correct place in the old repository You - and YOU ALONE - must do a complete new checkout of the lazarus module !! so mv lazarus lazarus.old cvs co lazarus because the repository information in you copy is wrong. Next time you add a directory, just do a cvs add dirname cd dirname cvs add *.* cvs commit -m 'xxxx' *.* Hope this helps... Michael (VC that is :) )

Reply by email

Baeseman, Cliff

Curtis Send it to I will put it in immediately about two hours from now.

Is the code split into includes if not I will do that for you it will be in the lcl directory.

Thanx

Cliff

Earlier message 61 lines
-----Original Message----- From: Curtis White Sent: Monday, July 26, 1999 2:20 PM To: Subject: [lazarus] CVS Updating I just finished making the initial working version of the TNotebook component. It needs more work, but I now have it working and want to commit it to CVS. But when I tried to commit it, CVS told me I don't have permission to do that. So how do I get permission to commit my code to CVS? I want to get it in there before someone changes gtkint again and I have to merge my changes back in to it. Curtis On 26-Jul-99 Michael Van Canneyt wrote: > > > On Sun, 25 Jul 1999, Michael A. Hess wrote: > >> I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the >> code from the main directory, all that is blown away. None of the code >> is there dude!!!!!!!! > > I have fixed this; do a 'cvs update -d lazarus' > > Cliff; it seems that you made a NEW repository, and all lcl stuff was > placed there. I have moved the code to the correct place in the old > repository > > You - and YOU ALONE - must do a complete new checkout of the lazarus > module !! > so > > mv lazarus lazarus.old > cvs co lazarus > > because the repository information in you copy is wrong. > > Next time you add a directory, just do a > > cvs add dirname > cd dirname > cvs add *.* > cvs commit -m 'xxxx' *.* > > Hope this helps... > > Michael (VC that is :) ) > _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Michael Van Canneyt
to Michael A. Hess: I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the code from the…
Michael A. Hess wrote
I just tried to get the lcl stuff. IT'S EMPTY. And since you removed the code from the main directory, all that is blown away. None of the code is there dude!!!!!!!!

I have fixed this; do a 'cvs update -d lazarus'

Cliff; it seems that you made a NEW repository, and all lcl stuff was placed there. I have moved the code to the correct place in the old repository

You - and YOU ALONE - must do a complete new checkout of the lazarus module !!
so

mv lazarus lazarus.old
cvs co lazarus

because the repository information in you copy is wrong.

Next time you add a directory, just do a

cvs add dirname
cd dirname
cvs add *.*
cvs commit -m 'xxxx' *.*

Hope this helps...

Michael (VC that is :) )

Reply by email