I inherited a project in which there is a toolkit on Qt, in particular, a plugin for importing SWF into an internal editor. It was written in the days of the old Qt Creator, I updated the plug-in's ad, it seems to have cursed it, the plugin compiles, but then something incomprehensible. in the process of lining issues

ld: warning: directory not found for option '-L / Users / rtn / Downloads / qt-creator-master / build / bin / Qt Creator.app/Contents/Frameworks

ld: library not found for -lCore

clang: error: linker command failed with exit code 1 (use -v to see invocation)

As I understand it, the problem is that the creator plugins are not built as libraries and are not linked. Search in folders did not give a result, I did not find anything similar. How to collect them, too, I do not understand

I collect under makos in Qt Creator 3.5.1

  • And this way to your creator? ( /Users/rtn/Downloads/qt-creator-master/build/bin/Qt Creator.app/Contents/Frameworks ) - ixSci
  • along the path /Users/rtn/Downloads/qt-creator-master/ are the qt creator source codes that I needed to start the project, I myself downloaded the creator from the site in the form of a dmg image and put a normal UPD application : I tried to create a new project The same problem - there are no libraries for linking. Maybe I needed another version of the creator? - Artem Kolosov
  • This should be the way to the creator, and not to the source, as I understand it. In general, read the manual for the assembly of the plug-in for the creator, everything should be there. - ixSci pm
  • Yes and no. This path is built from the variable QTCREATOR_SOURCES, but at the same time, next to them, a creator assembled in a package is searched, which must be built independently. - Artem Kolosov

1 answer 1

Solved the problem by rebuilding QtCreator from source, but on a more recent manual . As a result, I have a package with the necessary libs and source codes in the same directory, which allows plug-ins to be released in the release, if you want to debug them, you need to build a creator with debugging turned on, so that there would be a postfix d in the name.