https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #6 from Ralf Habacker <ralf.habac...@freenet.de> ---
(In reply to Ken Standard from comment #4)
> I did not mention this before, to keep the issues separate. But whether you
> are importing a project or using the import wizard, many things are not
> imported. I only mentioned this one.
You need to be more specific what 'many things are not imported' does mean
because they may have different reasons.
1. In the test case the private class is a forward declaration. Umbrello will
only be able to create an empty class for MyPrivateClass.
2. importing the following fragment
class MyClass {
public:
MyClass(const XYZ::AType &aparam);
};
gives umbrello no information, what XYZ is - it could be a namespace or a
class. In this case umbrello imports 'XYZ' as class with a stereotype
'class-or-package', which could be reassigned in the tree view.
3. Imported code may have some #include ... statements, which may not in the
default search path of umbrello, which is on unix
void CppImport::initialize()
...
ms_driver->addIncludePath(QLatin1String("/usr/include"));
ms_driver->addIncludePath(QLatin1String("/usr/include/c++"));
ms_driver->addIncludePath(QLatin1String("/usr/include/g++"));
ms_driver->addIncludePath(QLatin1String("/usr/local/include"));
const QStringList incPathList = Import_Utils::includePathList();
>From the call to Import_Utils::includePathList() a list of additional include
directories can be specified on the command line with the environment variable
UMBRELLO_INCPATH (path separator is ':' on unix/linux) before starting
umbrello.
You are refering to different cases ?
--
You are receiving this mail because:
You are watching all bug changes.
