Wish: adding links as project files
holle at almaden.ibm.com
holle at almaden.ibm.com
Mon Sep 27 18:59:05 BST 1999
Ok, whatever. You got that thing with including wrong. Copy the *.cpp and the
*.h files into your current directory and add them to the project by selecting
Add File to Project in the RFV (right mouse button). If you "upgrade" things,
then you need to redo the copying, but make shure no editor has that file opened
(apart from emacs).
Another way of going around the copies are *hardlinks*. You can create hardlinks
to files with ln <origin> <newplace/name>. When doing an ls -l on that file you
will see the reference counter showing a "2". As long as kdevelop does not
replace the file with a new one (rename old -> old~, create new) then everything
works. But if not, you have to copy ... It is worth trying.
- holger
Falk Brettschneider <gigafalk at geocities.com> on 27/09/99 00:54:07
Please respond to kdevelop at barney.cs.uni-potsdam.de
To: kdevelop at barney.cs.uni-potsdam.de
cc:
Subject: Re: Wish: adding links as project files
-------------- next part --------------
holle at almaden.ibm.com wrote:
>
> You are approaching the problem the wrong way.
> Under ... you generally *not* ... and I am *very
> strongly* against adding such a feature.
This is what already people from Redmont said.
> Here is what you normally do:
> Assuming the functions foo(), bar() and baz() are "shared" by two or more
> projects of yours.
> You would extract these three functions and the necessary support code from
your
> projects (yes from all) and make these functions become a shared and/or static
> library which you would link to your projects.
I don't want to have a lot of libraries because this forces me to manage
several projects. The only advantage I would have by using extra
libraries is to have already-compiled stuff. But this is not important
for me because compilation is fast enough on my machine.
My shared files have been changing all the time. That's why making
shared libs would only make it difficult and circumstantial to handle
(version, compatibility, ...)
Rene Märten <delta_x at gmx.net> wrote:
> you must include it instead of adding to project!
I don't want to include cpp files.
--
Ciao,
--Falk
More information about the KDevelop
mailing list