oclint-json-compilation-database | helper program that filters information | REST library

by oclint Python Version: Current License: BSD-3-Clause

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | oclint-json-compilation-database Summary

oclint-json-compilation-database is a Python library typically used in Web Services, REST applications. oclint-json-compilation-database has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However oclint-json-compilation-database build file is not available. You can download it from GitHub.

compile_commands.json is a JSON format compilation database. It maintains a list of sources with their build options. OCLint can leverage the information from this file to facilitate the inspection process. oclint-json-compilation-database helps extract and filter information from compile_commands.json, and invoke OCLint under the hook for analysis. Visit for documentation about using oclint-json-compilation-database.

Support

Quality

Security

License

Reuse

Support

oclint-json-compilation-database has a low active ecosystem.

It has 11 star(s) with 12 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

oclint-json-compilation-database has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of oclint-json-compilation-database is current.

Quality

oclint-json-compilation-database has 0 bugs and 0 code smells.

Security

oclint-json-compilation-database has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

oclint-json-compilation-database code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

oclint-json-compilation-database is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

oclint-json-compilation-database releases are not available. You will need to build from source code and install.

oclint-json-compilation-database has no build file. You will be need to create the build yourself to build the component from source.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of oclint-json-compilation-database

Get all kandi verified functions for this library.

oclint-json-compilation-database Key Features

No Key Features are available at this moment for oclint-json-compilation-database.

oclint-json-compilation-database Examples and Code Snippets

No Code Snippets are available at this moment for oclint-json-compilation-database.

Community Discussions

Trending Discussions on oclint-json-compilation-database

OCLint reports compiler errors due to its inability to find #import-ed header files

QUESTION

OCLint reports compiler errors due to its inability to find #import-ed header files

Asked 2018-Mar-02 at 19:00

I am trying to integrate OCLint 0.13 to check lint violations in my ObjC based iOS project.

As per this guide I created an aggregate target in Xcode to run a xcodebuild clean build followed by oclint-xcodebuild to generate a compile_commands.json. I am able to run the clang command from the generated compile_commands.json file. However, in html report generated by oclint-json-compilation-database command, while processing file like NEORepos/Public/ResourceObservables/NEOAggregatedObservable.h, I see compiler errors like 'NEOObservables/NEOObservable.h' file not found even though the said header file is present at NEOObservables/Public/Observables/NEOObservable.h.

How can I get rid of these compiler errors which are preventing some of my source files from being linted?

Running the clang command from compile_commands.json generates the .o file, but OCLint doesn't seem to be able to compile using the json file. I also tried adding a few more -I include paths, but it didn't help. All suggestions and pointers are welcome.

Here's a piece of (edited) log...

xcode_clean_build_command = xcodebuild -workspace 'Neo.xcworkspace' -scheme 'NeoSampleApp' -configuration 'Debug' clean build -dry-run -derivedDataPath /Users/username/Documents/git/ios-neo_linter/build/Neo -sdk iphonesimulator CLANG_ENABLE_MODULE_DEBUGGING=NO CODE_SIGNING_ALLOWED=NO CODE_SIGN_IDENTITY='' CODE_SIGNING_REQUIRED=NO ENABLE_BITCODE=NO COMPILER_INDEX_STORE_ENABLE=NO | tee xcodebuild.log

...

/oclint-xcodebuild

...

Generating the compile_commands.json ...

Picking NEORepos/Public/ResourceObservables/NEOAggregatedObservable.m Picking NeoSampleApp/main.m

...

Shortlisted files for linting (2 out of 283) and creating a new compile_commands.json

...

Compiling /Users/username/Documents/git/ios-neo_linter/NEORepos/Public/ResourceObservables/NEOAggregatedObservable.m - Failed Compiling /Users/username/Documents/git/ios-neo_linter/NeoSampleApp/main.m - Success Analyzing /Users/username/Documents/git/ios-neo_linter/NeoSampleApp/main.m - Done

...

Generating lint report (if any)...

...

Executing command: oclint-json-compilation-database -e Pods -v -- -list-enabled-rules -no-analytics -enable-global-analysis -verbose --report-type html -o oclint.html -extra-arg=-Wno-everything

...

/usr/local/bin/oclint -p /Users/username/Documents/git/ios-neo_linter -list-enabled-rules -no-analytics -enable-global-analysis -verbose --report-type html -o oclint.html -extra-arg=-Wno-everything /Users/username/Documents/git/ios-neo_linter/NEORepos/Public/ResourceObservables/NEOAggregatedObservable.m /Users/username/Documents/git/ios-neo_linter/NeoSampleApp/main.m

...

ANSWER

Answered 2018-Mar-02 at 19:00

The compiler error was due to the -dry-run flag that I was using. Since it was doing a dry run, it was not creating .hmap files that were needed (at least not in the right location) leading to .h file not found errors.

However, without -dry-run I would have to do a full build which is not acceptable for me. Will update if I find a solution with optimal performance.

Source https://stackoverflow.com/questions/48881024

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install oclint-json-compilation-database

You can download it from GitHub.
You can use oclint-json-compilation-database like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: