...
Anyways, the little pop-up at the bottom says I should check the application log... but it doesn't tell me where this log is located at all and I can't find it anywhere.
Can you guys help me out by telling me where to find out the application log?
thanks
#include <sdk.h> // Code::Blocks SDK
#include <configurationpanel.h>
#include "HelloWorld.h"
#include <manager.h>
#include <logmanager.h>
// Register the plugin with Code::Blocks.
// We are using an anonymous namespace so we don't litter the global one.
namespace
{
PluginRegistrant<HelloWorld> reg(_T("HelloWorld"));
}
// constructor
HelloWorld::HelloWorld()
{
// Make sure our resources are available.
// In the generated boilerplate code we have no resources but when
// we add some, it will be nice that this code is in place already ;)
if(!Manager::LoadResource(_T("HelloWorld.zip")))
{
NotifyMissingFile(_T("HelloWorld.zip"));
}
}
// destructor
HelloWorld::~HelloWorld()
{
}
void HelloWorld::OnAttach()
{
// do whatever initialization you need for your plugin
// NOTE: after this function, the inherited member variable
// m_IsAttached will be TRUE...
// You should check for it in other functions, because if it
// is FALSE, it means that the application did *not* "load"
// (see: does not need) this plugin...
}
void HelloWorld::OnRelease(bool appShutDown)
{
// do de-initialization for your plugin
// if appShutDown is true, the plugin is unloaded because Code::Blocks is being shut down,
// which means you must not use any of the SDK Managers
// NOTE: after this function, the inherited member variable
// m_IsAttached will be FALSE...
}
int HelloWorld::Execute()
{
// do your magic ;
if( !IsAttached() )
return -1;
Manager::Get()->GetLogManager()->Log( _("Hello World!") );
return 0;
}
Unfortunately, I don't understand what's going on because it compiled alright, so I would have though that all the symbols would have been taken care of? I will post my code below:I think you are missing to provide a (zipped) manifest.xml file for the plugin (and putting it into the right place). Look at other plugins how they do that... for example the envvars plugin. Notice the post build steps and that the zip archive has to have the same name as your plugin (case sensitive on linux). Anyways... it's really simple! :-)
you have to add VENDOR=cb to the makefile options.You should *not* do that. This is deprecated and was the root of many issues. Just leave the vendor as it is (don't provide this for the compilation of wx).
You should *not* do that. This is deprecated and was the root of many issues. Just leave the vendor as it is (don't provide this for the compilation of wx).
So how can I build a plugin that will correctly load with a nightly build?
you need to make sure you link against the codeblocks.dll and wxmswXXXXX.dll in the nightly build and not against those in your compiled cb and wxwidgets sources.
And how is wxWidgets built to get the wxmsw28u_gcc_cb.dll file provided with the nightly builds?
Partially. Killerbot does but he knows exactly what he is doing. I don't and I believe Yiannis and Thomas don't, too. If you compile wx for C::B only you *can* do this but you better shouldn't. Search the forum for more information on vendor=cb.QuoteAnd how is wxWidgets built to get the wxmsw28u_gcc_cb.dll file provided with the nightly builds?Correct me if I'm wrong, but I imagine they do use VENDOR=cb.
So how can I build a plugin that will correctly load with a nightly build?
Can you guys help me out by telling me where to find out the application log?
Hi everyone,
I find that nobody is answering the original question:Can you guys help me out by telling me where to find out the application log?
Does the application log really exist? And if yes, where is it?
Thanks,
Ankur
The lower window with build log and build messages; right click on its title bar and see if you can turn it on.
The last few builds, I think it might have been called "Code::Blocks" under toggle option.
Tim S
I confirm. On startup, the log does not show up until the user scrolls in the CodeBlocks log window.This "bug" is there for ages is is IMHO actually a WX issue. I have the same in several other wx apps.