Giter VIP home page Giter VIP logo

Comments (3)

mlangkabel avatar mlangkabel commented on August 10, 2024

Hi @jonesinator. Thanks for your really comprehensive report on that issue! Right now there are only a handful of file extensions that Coati detects by default.
In the current release of Coati you can extend that list by manually editing your .coatiproject file. To do so you need to add these extensions as subnodes of the source node in the following way:

<source>
   <extensions>
      <header_extensions><!-- STRING: extension for header/include e.g. .h --></header_extensions>
      <source_extensions><!-- STRING: extension for source e.g. .cpp --></source_extensions>
   </extensions>
   ...
</source>

For the case you mentioned above I would recommend adding the .ipp extension as a source_extension.
Editing the .coatiproject file by hand should be only a temporary solution while we are working on adding these settings to the project settings screen.

from sourcetrail.

jonesinator avatar jonesinator commented on August 10, 2024

Thanks! I'm glad there's already a workaround in the product. I had to use header_extensions instead of source_extensions, but otherwise this worked for me. When I used source_extensions it complained about redefinition of foo<T>::go() I guess since the function was defined in foo.ipp and again by inclusion in main.cpp.

In case anyone has the same issue, the exact XML I used is below. It seems like specifying a single header_extensions entry overrides the default entries instead of adding to them, so I had to have a tag for both hpp and ipp even though hpp is normally automatically detected by Coati.

<source>
        <extensions>
            <header_extensions>.hpp</header_extensions>
            <header_extensions>.ipp</header_extensions>
        </extensions>
</source>

from sourcetrail.

mlangkabel avatar mlangkabel commented on August 10, 2024

@jonesinator: On a second thought adding the extension as a ´header_extension´ makes sense, as your compiler also wouldn't create a translation unit for that file.
Regarding the overridden header extensions: We implemented that policy so that one can get rid of the extensions we predefined (in case you don't want to analyze .h files ;) ). I think this will be much clearer once we added this setting to the GUI (I opened a new issue #49 for that).

from sourcetrail.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.