pmaillot / X32-Behringer

This GIT repo (C language) holds applications and utilities for the Behringer X32 and M32 mixing consoles. Additional details, documentation, implementation examples and apps can be found in my website:
https://sites.google.com/site/patrickmaillot/x32
234 stars 41 forks source link

Thanks - and compiling hints #13

Closed phedders closed 5 years ago

phedders commented 6 years ago

Many thanks for these awesome utils and the docs you've written - they are much appreciated.

I have a few ideas for tweaks I'd like to make - for example simply changing the default IP address to a name "x32" that can be set in /etc/hosts (or the windows equiv)

But I havent worked out how to compile these utils (linux, standard GCC7.3 etc)

I'd contribute a simple Makefile once I've got it.... could you drop some hints?

pmaillot commented 6 years ago

Hello, Thanks for your kind words. I typically use Eclipse (Windows/Linux/Mac) for my projects.Typically separated apps with a utility library (I'll list the modules) that I static-link with the applications. I'll check what kind of makefile is generated by Eclipse, and will forward this. Sometimes during the coming week-end.

-Patrick

phedders commented 6 years ago

Oh Eclipse... havent used that in years! Thanks for digging out the make process.

pmaillot commented 6 years ago

Yes. It is nevertheless quite useful and easy to work with. Not a bad IDE for working in C under Windows/Mac. To get back to you initial question: The following files are compiled and assembled as a library I called X32_lib

TestParams.c validateIP4Dotted.c X32_cparse.c X32_dump.c x32_parse.c X32_scene2X.c X32_sprint.c X32Connect.c

Be aware that not all programs aim or will compile for unix environments.

A typical compile line will be: $CC /application.c -O3 -Wall -I /X32_lib -o /application Under Windows, I typically use mingw 32bits (generates smaller files than the 64 bits version)

Hope this helps, -Patrick

phedders commented 6 years ago

On Sun, 2018-06-10 at 10:25 -0700, Patrick-Gilles Maillot wrote:

Yes. It is nevertheless quite useful and easy to work with. Not a bad IDE for working in C under Windows/Mac. To get back to you initial question: The following files are compiled and assembled as a library I called X32_lib TestParams.c validateIP4Dotted.c X32_cparse.c X32_dump.c x32_parse.c X32_scene2X.c X32_sprint.c X32Connect.c Other programs (applications) are basically complied and the X32_lib library is statically linked to generate said programs. A few number of programs include separate .o files which are added at link time in order to generate applications. Be aware that not all programs aim or will compile for unix environments. A typical compile line will be: $CC /application.c -O3 -Wall -I /X32_lib -o /application Under Windows, I typically use mingw 32bits (generates smaller files than the 64 bits version) Hope this helps,

Yes that X32_Lib was clearly missing from my understanding - many thanks, I'll try and get some time to tweak tonight.

-Patrick — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

pmaillot commented 6 years ago

Just updated the GitHub repo to reflect this. There's now an x32l8b directory with files inside.

Le lun. 11 juin 2018 8:37 AM, phedders notifications@github.com a écrit :

On Sun, 2018-06-10 at 10:25 -0700, Patrick-Gilles Maillot wrote:

Yes. It is nevertheless quite useful and easy to work with. Not a bad IDE for working in C under Windows/Mac. To get back to you initial question: The following files are compiled and assembled as a library I called X32_lib TestParams.c validateIP4Dotted.c X32_cparse.c X32_dump.c x32_parse.c X32_scene2X.c X32_sprint.c X32Connect.c Other programs (applications) are basically complied and the X32_lib library is statically linked to generate said programs. A few number of programs include separate .o files which are added at link time in order to generate applications. Be aware that not all programs aim or will compile for unix environments. A typical compile line will be: $CC /application.c -O3 -Wall -I /X32_lib -o /application Under Windows, I typically use mingw 32bits (generates smaller files than the 64 bits version) Hope this helps,

Yes that X32_Lib was clearly missing from my understanding - many thanks, I'll try and get some time to tweak tonight.

-Patrick — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pmaillot/X32-Behringer/issues/13#issuecomment-396137234, or mute the thread https://github.com/notifications/unsubscribe-auth/APOZ_kvLy-FuDfzeoIsBjx1VY0IrQO3Zks5t7hAugaJpZM4UgJ3V .