Translations:KDevelop4/FAQ/40/da: Difference between revisions

Latest revision as of 16:36, 16 January 2012

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (KDevelop4/FAQ)

For cases where '''KDevelop''' is still not figuring out the include path properly after you have configured your build toolchain, you can manually add include paths on a per-directory basis into a <tt>.kdev_include_paths</tt> file. This can be done from inside '''KDevelop''' by running the "solve problem" wizard associated with a "could not find include file" problem, e.g. by hovering the problematic <code>#include</code> line.

I tilfælde, hvor KDevelop stadig ikke kan finde alle include-stierne efter at du har konfigureret din værktøjskæde til bygning kan du manuelt tilføje include-stier for hver mappe i en .kdev_include_paths-fil. Dette kan gøres fra KDevelop ved at køre guiden "løs problem" knyttet til problemet "kunne ikke finde include-file", fx ved at lade musen svæve over den problematiske #include linje.