Hi,

if writing an IDE extension, how would the setup for testing it look like?

Assuming:
- the package registers a menu entry
- it does some design time manipulations according to the users/programmers wishes

The code is written and compiled. Then it needs to be installed in the IDE and tested. How can I do it in a handy way?

TIA,
Marc

Marc Santhoff wrote

The code is written and compiled. Then it needs to be installed in the IDE and tested. How can I do it in a handy way?

You can debug the IDE by opening lazarus.lpi project and pressing F9. Lazarus must be built with debug info before that. Another way to debug is by adding DebugLn() calls and checking their output in console or log file.

Juha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20160606/19795c66/attachment.html>

OK, so there is no other way but actually compiling the extension in.

What I will try is to make the shim between IDE coupling an the rest as thin as possible, so anything else can be tested separately before.

Thanks,
Marc

Hint: you can have multiple Lazarus instances, using the --pcp command line switch.

OK, so there is no other way but actually compiling the extension in.

Well, you can create a project and compile your extension into that. Of course than you can only test a few parts.

What I will try is to make the shim between IDE coupling an the rest as thin as possible, so anything else can be tested separately before.

Good idea.

Mattias

Ah, I didn' think about it, thanks.

A bit confusing at first, solving the chicken-egg-problem by getting another chicken... ;)

Getting hungry now,
Marc