Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
General (but related to Code::Blocks) / Re: Policies for plug in dev
« Last post by stahta01 on April 26, 2017, 09:04:17 pm »
The license we use for the SDK is LGPL-3.
The only thing you should do is to be compliant with this license.
What it really means in terms of actions, I'm not sure.

Unless it changed, I believe a linking exception was added to the LGPL-3 used by CB's SDK; but, I have NOT really read it since it changed from L/GPL2 to version 3.
If still true, you need to make available all the source code changes  made to CB's SDK; but, you need NOT make your plugin source code available if it just dynamically links to the SDK. But, some complex plugins do need to edit the SDK source code to work; you will need to make available those changes and you need to make available all of the source code from the CB project that you plan to distribute.

NOTE: The art work used by CB might be under a separate license from LGPL-3. 

Edit: http://www.gnu.org/licenses/lgpl-3.0.html; I did NOT see the old linking exception in the SDK source code; but, I think LGPL allows the linking exception, the words were too confusing for me to be sure that is true.

Tim S.


 
32
General (but related to Code::Blocks) / Re: Policies for plug in dev
« Last post by oBFusCATed on April 26, 2017, 08:32:09 pm »
The license we use for the SDK is LGPL-3.
The only thing you should do is to be compliant with this license.
What it really means in terms of actions, I'm not sure.
33
Hello guys,

i create this post 'cause i need to copy my binaries to a remote target device (i'm running C::B on windows)and also launch gdbserver from the host.

I tried all the suggestions posted in the following topic: http://forums.codeblocks.org/index.php?topic=19279.0 but, unfortunately, these didn't work for me. I'm on 16.01 CB.

Thanks in advance for your assistance.

MB
34
General (but related to Code::Blocks) / Policies for plug in dev
« Last post by usercb2017 on April 26, 2017, 02:53:12 pm »
Hello team,

As a plugin developper, i would like to know what should be done to use these plugins for commercial use in a compliant way.

Coud you please, inform me about the requirements to do so?

Thank you

MB
35
Absolutely unrelated to Code::Blocks and therefore violating our forum rules.

Topic locked !
36
I exactly described what I get with codeblocks
when I try to compile ECOMcat.c

all I get is Hello World, default main.c input.
Try it yourself.

Ok, I need to get now ecommlib.dll from genuine developer.

thank you
37
I mean ECOMcat.c should be renamed to main.c first
since otherwise all build and compilation is done for a default main.c Hello World file coming with codeblocks

After reading this i am dead sure whatever "project" you have in your mind, drop that idea. You have no idea about coding at all, i doubt it looks much different in the area of can networking.

Does the CB site support black or white hat code crackers; or in other words script kiddies?

Tim S.
38
I mean ECOMcat.c should be renamed to main.c first
since otherwise all build and compilation is done for a default main.c Hello World file coming with codeblocks

After reading this i am dead sure whatever "project" you have in your mind, drop that idea. You have no idea about coding at all, i doubt it looks much different in the area of can networking.
39
this are quite mixed applications with python, from your posting i think this is quite over your head, and i don't think anyone has the time, to give you a step by step instruction.
The documentation of all this is really poor, or non existent. This does not help either...

Thank you  BlueHazzard for your kind and excellent reply.

You are exactly right about the missing documentation but GitHub projects don't come with manual by default, so I have contacted genuine project developers to get helpful hand
and all I have if code from GitHub.


The easiest way is to create a project and add the files:
Simply create a console project , delete the main.cpp and add the c and h files with Project->Add files

Ok. I know now how to add files to the project.

Quote
Let me know if C and C++ compilers coming with CodeBlocks are fit to compile the above code from GitHub,
if not, should I use MS Visual Studio and MS C C++ compilers ?
No idea... you have to look trought the code and look if there are some msw specific compiler options. You can try the import plugin of Codeblocks: File->Import project->MS Visual studio project file

I tried MS win32 to build console app.

Quote
If source code is not renamed to main.c
default main.c code gets compiled - Hello World every time.
well in main.c is the main function... You have to add the source files to the project to let codeblocks know what you want to compile

Ok.
I mean ECOMcat.c should be renamed to main.c first
since otherwise all build and compilation is done for a default main.c Hello World file coming with codeblocks

Since
ecomcat\content\code\ecomcat_api\Debug
directory comes with precompiled binaries

what is missing is ecommlib.dll to be built

ecommlib.lib is coming with
ecomcat\content\code\ecomcat_api\ecomcat_api
directory

More about ecommlib.dll comes from
https://www.cancapture.com/sites/default/files/downloads/ECOM_Developers_Library_Reference.pdf


Ok, I am fully aware I need to offer bounty.
All I need is to build simple application to perform AUTOPARK function for a CAN bus controllable car.
AUTOPARK should work with park cameras and ultrasonic parking sensors.

So I need budget to succeed.

Thank you once again.
codeblocks is really great toolbox to build C, C++ projects if you live on Windows XP.

You are free to join my AUTOPARK project.
40
Find the gdb pretty printer script in the wx project for your version and search how to enable it in codeblocks.
You need python enabled gdb for this to work.
Pages: 1 2 3 [4] 5 6 7 8 9 10