specialisttore.blogg.se - Clion community edition

Project can be compiled correctly, but highlighting, completion, refactorings, etc.Keymaps and useful shortcuts, what to do if a shortcut is not working?.Is there a community edition for CLion? Is CLion available as a plugin for IntelliJ IDEA?.I can’t find some functionality in CLion.What to do if debugger doesn't work as expected?.In order to facilitate communication, may I suggest that you proceed to our bug tracker, file and issue and assign it to me? We'll continue from where we left off then. Finally, can you open the project as a compilation database project in CLion (open compile_commands.json instead of the Makefile)? Are you experiencing the same problems then?.Can you share the output of Show Compiler Info action for each of your source files?.If you #include any of the standard headers into your source files ( stdio.h, stdint.h, etc.) - can you navigate to those standard headers from a Makefile project opened in CLion?.Is /opt/local/include readable and does it indeed contain OpenABE headers?.or, finally, compile and link implicitly (rename LIBS to LDLIBS):Īnyway, none of the above would prevent CLion from opening your project.

compile using the implicit rules and only link explicitly:.

stop listing test_api.o and attributeAuthority.o as target pre-requisites (since you're manually compiling them anyway), or.

Uri Blumenthal, I've re-created your project (using dummy OpenABE headers in /opt/local/include) and CLion opened the project w/o a single warning, with the headers being fully resolvable.īTW, there's an issue with your Makefile: each source file gets compiled twice, so you probably should either

$(CXX) -o attributeAuthority attributeAuthority.cpp $(CXXFLAGS) $(LDFLAGS) $(LIBS)ĪttributeAuthority.cpp compile_commands.json include mon README.md test_api.cpp $(CXX) -o test_api test_api.cpp $(CXXFLAGS) $(LDFLAGS) $(LIBS)

LDFLAGS += $(shell pkg-config -libs libpistache) LIBS := -lcrypto -lrelic -lrelic_ec -lopenabeĬXXFLAGS += $(shell pkg-config -cflags libpistache) Make: Leaving directory '/Users/ur20980/src/security'ĬXXFLAGS := $(CXX11FLAGS) $(OS_CXXFLAGS) -pthread -Wall -g -O2 -DSSL_LIB_INIT -I$(INCDIR) -std=c++14 Make: Entering directory '/Users/ur20980/src/security'Ĭlang++ -I/opt/local/include -march=native -pthread -Wall -g -O2 -DSSL_LIB_INIT -I/opt/local/include -std=c++14 -c -o test_api.o test_api.cppĬlang++ -o test_api test_api.cpp -I/opt/local/include -march=native -pthread -Wall -g -O2 -DSSL_LIB_INIT -I/opt/local/include -std=c++14 -L/opt/local/lib -lcrypto -lrelic -lrelic_ec -lopenabeĬlang++ -I/opt/local/include -march=native -pthread -Wall -g -O2 -DSSL_LIB_INIT -I/opt/local/include -std=c++14 -c -o attributeAuthority.o attributeAuthority.cppĬlang++ -o attributeAuthority attributeAuthority.cpp -I/opt/local/include -march=native -pthread -Wall -g -O2 -DSSL_LIB_INIT -I/opt/local/include -std=c++14 -L/opt/local/lib -lcrypto -lrelic -lrelic_ec -lopenabe Rm -rf *.o *.dSYM test_api attributeAuthority To the PKG_CONFIG_PATH environment variable Perhaps you should add the directory containing `libpistache.pc' Package libpistache was not found in the pkg-config search path. My complaint is about inability to locate headers for `openabe` that reside in `/opt/local/include`. Both require `openabe` package that is present. One of those C++ files requires `pistache` package that is currently missing. cpp files and two executables built from each of them. Just a small C++ Makefile project, with two. some Makefile projects explicitly set `MAKEFLAGS` (or, alternatively, `GNUMAKEFLAGS`), overriding the default values