User forums > Using Code::Blocks

How to build the .plw plug-in

<< < (3/4) > >>

Дмитро:
When I add ../path/to/your/sdk/libgcc.wXX/ida.a -Wl, - dll -shared whether to place in one line, together the path and these -Wl, -dll -shared, or Otherwise to place them in other place?

BlueHazzard:
Ok, now i think i know what you want. You want to build this IDA plugin with codeblocks?

Ok, so i think the best way is to go the dev c++ way...
You have to add the paths for libraries like

--- Quote ---/path/to/your/sdk/libgcc.wXX/
--- End quote ---
to Project->Settings->Build options->Search directories->Linker

Libraries like

--- Quote ---ida.a
--- End quote ---
you add to   Project->Settings->Build options->Linker settings->Link libraries

You can also place it combined in Project->Settings->Build options->Linker settings->Other linker options but then you have to add the "-l" for library:

--- Code: ----lpath/to/your/sdk/libgcc.wXX/ida.a -Wl, - dll -shared
--- End code ---

Linker options like

--- Quote ----Wl, - dll -shared
--- End quote ---
are set in Project->Settings->Build options->Linker settings->Other linker options
(you can distinguish linker and compiler settings the most time by the "-Wl," part. this means linker option)


--- Quote ---Just a note here - it's usually best to start with
../
, because msys seems to get confused
with just
 /
, and tries to reference it from the root of the msys directory.
--- End quote ---
i would ignore this note...


--- Quote ---I do not know how Under
C ++ compiler
, add:
-DWIN32 -D__NT__ -D__IDP__ -v -mrtd
--- End quote ---
this are mixed options...
-D is for defines. you can add all this  to other compiler options: Project->Build options->Compiler settings->Other compiler options:

--- Code: ----DWIN32 -D__NT__ -D__IDP__ -v -mrtd
--- End code ---

or you splitt the "-D" options to "#defines" Project->Build options->Compiler settings->#defines:

--- Code: ---WIN32
__NT__
__IDP__

--- End code ---


--- Quote ----v -mrtd
--- End quote ---
i don't know this options... But compiler options are always set in Project->Build options->Compiler settings->Other compiler options

I hope this helped a bit. If not i can try to write a more detailed guide, on the base of you instructions. But i can not test it because i have to IDA and i can not pay for it (it would be a cool tool...)
If you have problems compiling, please remember this link: http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F and always post a full build log.

Greetings

Дмитро:
If not i can try to write a more detailed guide, on the base of you instructions. But I can not test it because it has an IDA and I can not afford it
Thank you! Yes, this tool is cool, cool tool, but they need to be able to use. There are so many different possibilities, many buttons, but it takes a long time to get used to. Just do not know exactly which buttons to press and how to use it. And I, too, am still extremely poor at knowing how to use this tool.

Дмитро:
E:\PL\PL1\pl1.cpp|70|error: 'init' was not declared in this scope|

extern "C" plugin_t PLUGIN = {
IDP_INTERFACE_VERSION,
0,
init,
term,
run,
comment,
help,
wanted_name,
wanted_hotkey
};

There are still errors, which indicates either my incorrect settings in the code blocks, or my incorrect IDA, or somewhere else wrong.

I also use my old familiar codeblocks, a good handy very familiar one, with the GNU GCC g ++ compiler, which is all good, and not any other tool or compiler. :)

Дмитро:
In one box with IDA there are many examples. They are for self-compilation. These examples are all provided with a makefile. How is it better to open it with codeblocks? Is it really necessary to create a project? Perhaps it is enough to specify only the makefile, would that be better?

Navigation

[0] Message Index

[#] Next page

[*] Previous page