User forums > Using Code::Blocks
Cannot find libs ... but they are there...
msdobrescu:
First, I do not port, I have to use it.
Secondly, it seems I misinterpreted the error.
I took the following as it was somehow compiled twice and I've wondered if C::B generated a malformed build command.
--- Code: ---M:/Creative/Adobe/dev/jScriptor/Adobe/sdk/Adobe Illustrator CC_2015.3 SDK/illustratorapi/illustrator/IAIAutoBuffer.cpp:55: multiple definition of `ai::SPAlloc::AllocateBlock(unsigned long long)'
.objs\Adobe\sdk\Adobe Illustrator CC_2015.3 SDK\illustratorapi\illustrator\IAIAutoBuffer.o:M:/Creative/Adobe/dev/jScriptor/Adobe/sdk/Adobe Illustrator CC_2015.3 SDK/illustratorapi/illustrator/IAIAutoBuffer.cpp:55: first defined here
--- End code ---
If this is not the case, thing is solved.
+ It's Adobe API poorly documented. That statement is not clear. I've no idea what "core application" means as I build a plugin.
msdobrescu:
One question though.
When I add files to the project, are they automatically set to compile and link?
Especially headers, how are to be set concernng compiling and linking?
stahta01:
--- Quote from: msdobrescu on August 20, 2016, 04:45:31 pm ---First, I do not port, I have to use it.
Secondly, it seems I misinterpreted the error.
I took the following as it was somehow compiled twice and I've wondered if C::B generated a malformed build command.
--- Code: ---M:/Creative/Adobe/dev/jScriptor/Adobe/sdk/Adobe Illustrator CC_2015.3 SDK/illustratorapi/illustrator/IAIAutoBuffer.cpp:55: multiple definition of `ai::SPAlloc::AllocateBlock(unsigned long long)'
.objs\Adobe\sdk\Adobe Illustrator CC_2015.3 SDK\illustratorapi\illustrator\IAIAutoBuffer.o:M:/Creative/Adobe/dev/jScriptor/Adobe/sdk/Adobe Illustrator CC_2015.3 SDK/illustratorapi/illustrator/IAIAutoBuffer.cpp:55: first defined here
--- End code ---
If this is not the case, thing is solved.
+ It's Adobe API poorly documented. That statement is not clear. I've no idea what "core application" means as I build a plugin.
--- End quote ---
If you DO NOT wish to port it to a different compiler; then use a supported Compiler!!!!!!
--- Quote ---***********************************************************
3. Development Environments
***********************************************************
The following platforms are supported for the development of plug-ins:
Mac OS:
OS: Mac OS 10.9
IDE: Xcode 7.2.1
Compiler for C/C++: com.apple.compilers.llvm.clang.1_0
Base SDK: OS X 10.11
OS X Deployment Target: OS X 10.9
Windows:
OS: Microsoft Windows 7 (including 32 bit)
IDE: Microsoft Visual C++ 14 (Visual Studio 2015)
For more details, see the ”Porting Guide."
--- End quote ---
stahta01:
--- Quote from: msdobrescu on August 20, 2016, 06:21:09 pm ---One question though.
When I add files to the project, are they automatically set to compile and link?
Especially headers, how are to be set concernng compiling and linking?
--- End quote ---
Source files default to compiling and linking.
Header files default to NOT compiling and NOT linking.
Tim S.
stahta01:
Please give up on using the GCC compiler!!
If you do NOT want to; then, I suggest you need to ask someone you know and trust to explain why what you are doing is a waste of time.
FYI: Code::Blocks is a IDE that works with more than one compiler.
IF someone told you to use Code::Blocks it does NOT mean you have to use the GCC Compiler!
HINT: You are trying to build a plugin, the plugin ABI must match what the application is expecting!!
That means using the compiler the application tells you to use in nearly all cases where the API is C++.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version