Kylix zatuhnuti

Števlík Marián Marian.Stevlik na merlin.cz
Čtvrtek Září 19 07:40:50 CEST 2002


Cau cau
Mne instalacia i spustenie prebehlo v poriadku na 7.3
Mal som vsak z Borland stranok TXT subor, kt. mi povoli pouzivat K3E 30dni
(Je potreba tam vyplnit registraciu a na uvedeny mail ti pride ten TXT)

Ala nasiel som na inete toto (i ked ja som to nepotreboval pouzit):

Getting K3OE working on Red Hat 7.3
After completing the registration/survey required by Borland, I downloaded
the tar ball for Kylix 3 OE. It is huge. At least the version I downloaded
was more than 300 megabytes. That's more than ten times the size of Kylix 2
OE.

You can install Kylix either as root or as a normal user. I chose to install
as root. It's straightforward. After tar decompresses and reassembles
everything, you find you have a new subdirectory named kylix3_open.

Contained in that directory are a README, an INSTALL and a PREINSTALL text,
a full copy of the license, a directory of pre-installation compatibility
checking tools, a directory containing distribution/version specific
patches, and of course the install script itself. On my system (a 1-GHz
Athlon with 512 megabytes of RAM), it took very little time to do the actual
installation once tar was finished. I started the install by entering sh
setup.sh in a terminal window and about a minute later it was soup.

Unfortunately for me, the soup was too hot. I had several problems
immediately. As I searched USENET for solutions, the first thing I became
aware of was that Red Hat 7.3 is not yet supported. Bummer. It also became
clear that other Red Hat 7.3 users were having the same problems.

I asked Borland for tips and workarounds, but they responded they would much
prefer to help me work on a supported platform. Of course, I wanted them to
help me with my problem, but I do understand where they are coming from. In
fact, I agree with them.

Let me say this again. I would recommend that if you have a need to use
Kylix 3 for real development that you do so only on supported distributions.
Software development is not the sort of thing where you need to go out of
your way to find challenges. It has perils enough of its own.

Just call me a stubborn, hardheaded geek, but I plowed ahead with RH 7.3. I
picked up tips here and there on the borland.public.kylix.* newsgroups, and
when something didn't work one way I tried it another. The problems I ran
into were:



application freeze-up in file open dialogs
inability to compile even the example projects
missing menu items
I got around the first problem by grabbing a stock version of the kernel
(2.4.19) from www.kernel.org and installing it. It's been awhile since I've
had to -- or simply wanted to -- build a kernel. It's much easier now than
the first couple of times I did it.

After unpacking the tarball, I went into the newly created /linux directory
and entered make clean at the command line. Then came make xconfig. That
gave me the opportunity to configure the kernel for my needs. In my case, it
was simply a matter of making sure I added module support for USB and for my
NIC. If you're doing this for the first time, you'll want to have a good
handle on your hardware makeup before beginning.

After configuring the kernel build, I ran the following in order:

make dep
make
make install
make modules
make modules_install

In the past, it would be time to reconfigure lilo by editing the
configuration file and rerunning lilo itself. However, since I had accepted
the default grub (grub stands for GRand Unified Bootloader) when I installed
Red Hat 7.3, it wasn't necessary. I peeked at the grub configuration file to
see how difficult it was going to be to add the new kernel. Guess what? It
was already there. I didn't need to run anything to select it. Good on grub.

After rebooting with the new kernel (grub still offers me a choice of when
one to load), I started Kylix from a terminal window with the command
startbcb. I was able to pick a file or project to open without a freeze.
That's the good news. The bad news is I was unable to compile any of the
example projects.

On a hunch, I decided to run Kylix as root. It worked, all the example
projects compiled! Now I was getting somewhere. I decided to check the GNOME
menus while still root. There were the missing Kylix menu items.

Running as root unnecessarily is always a bad idea, so I decided to
reinstall K3OE as a normal user. I ran the uninstall program that had been
placed in the kylix3 directory, then removed everything I could find in my
home and root directory that started with .kylix or .borland.

When I tried to reinstall Kylix, it complained that it was already on my
system, in the directory that had just been removed. I used Google to search
the newsgroups for the exact error I was getting and found that by appending
"-m" to the setup script command line, I could suppress the error and
reinstall. I did just that.

Finally, I could compile the examples as a normal user. I also compiled a
quick test of my own, just to be sure. I could also launch Kylix from my
Ximian GNOME desktop. I was happy at last. Remember, I did this for fun, for
the sake of my geek ego. Who knows what additional problems I may run into a
little further down the path?

The moral is this. Do not try this at home. Do not run Kylix 3 on an
unsupported distribution unless it makes no difference to you if the product
works or not. If you're like me and just want to learn and play with it,
fine. As a matter of fact, now that I have it installed and (apparently)
working, that's exactly what I'm going to do. In the weeks ahead, I'll
report on what I've learned about Kylix 3 OE and its C++ capabilities

Stevlik Marian
Software Development Specialist
MERLIN
Stefanikova 32
150 00 Prague 5
Czech Republic
e-mail: marian.stevlik na merlin.cz
tel: +420 2 41010111 (181)
ICQ: 38493645


Další informace o konferenci Linux