| Summary: | Support adding any kind of file to targets in the buildsystem | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Sylvain Joyeux <sylvain.joyeux> |
| Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
True. The hackish workaround - create "blank" files with the needed name and add them to the target. This will get the build system to do the right thing. There need be explicit support though, I agree. The workaround I use now is to manually edit the Makefile.am and then reload the project. Since I don't create skel and stub files very often, it's enough for now. The bugreport was just to get sure it would be fixed in future releases. I don't think its reasonable to completely limit the files that can be added to a target, the file-dialog of course should supply a reasonable default filter for code-files, but you shouldn't limit the user to add other file types. Changing the summary accordingly this should work nowadays actually. in kdev4 |
Version: CVS HEAD (using KDE KDE 3.2.0) Installed from: Debian testing/unstable Packages The KDE build scripts support dcopidl. You just have to add "foo.skel" and/or "foo.stub" files in the _SOURCES field, and the scripts will build the corresponding foo_skel.cpp and foo_stub.{cpp,h} for you, using foo.h The problem here is that the automake part does not support adding non-existent files.