I am trying to build a UBOOT standalone application.
Looking at the README and the minimal documentation on this, I am curious.
Is the hello world example standalone, simply just compiled/cross-compiled the same way any other application is? Obviously for whatever the target architecture is.
Do I need to use makeelf or something to get a .bin file?
Related
I'm following the instructions here: https://github.com/symless/synergy-core/wiki/Compiling for compiling on OSX. I've "finished" everything. But I don't understand what to do to install synergy once the compiler has completed? I was expecting a nice output directory somewhere with a synergy.app or something in it. Am I missing something? I've used the GUI method using QT to compile the code as I didnt scroll down far enough initially to realise you can do it on the command line. But either way I've managed to get to the end of the instructions for compiling and I'm a little lost now.
Thanks
Once it's compiled, Synergy binaries are outputted to the build/bin directory inside whatever directory you cloned the Synergy source to (it was ~/git/synergy-core in my case).
You can run ~/git/synergy-core/build/bin/synergy (replacing with whatever your path is) to start the Synergy configuration UI which lets you configure your server or client as desired.
Is it possible to include standalone applications/startup scripts in the u-boot bootup process, and what is the available hooks?
So far I can see from the hello_world example how to compile a standalone application in C, but it still needs to be loaded manually through tftp which I don't want to do.
EDIT: I have found several "hooks" listed in common.h such as
last_stage_init()
board_late_init()
Where can I find an idea of the proper workflow to add an application to make adjustments to the environment variables?
The basic answer here is that you can have whatever you want run in the CONFIG_BOOTCOMMAND variable and that in turn can load and 'go' your application from wherever you have stored it on the device.
I wanted to use a u-boot startup script but did not know how to proceed and wrongfully used the term application.
I now use the hooks specified in board_r.c, for example misc_init_r() and last_stage_init() where I put my startup scripts required before boot.
Just remember to enable these functions with #define CONFIG_LAST_STAGE_INIT and #define CONFIG_MISC_INIT_R()
I am trying to dynamically link to a custom dynamic library in an OSX application. For various reasons, I don't want to have specify environment variables after the build. I want my build environment to provide everything needed to run the application.
I am compiling the application with gcc using a makefile (actually, I a script that makes calls to qmake and does some automated editing.). On linux I would just do:
-Wl,-rpath,<path/to/dynamic/library>
but for whatever reason OSX doesn't abide by these rules. I keep getting
#rpath/mylib.dylib Library not loaded
when I try to run the app.
I hope this is clear. I want the app itself to know where to look for mylib.dylib. I know how to do this in Xcode with LLVM, but it would be nice if I could do it with a makefile and gcc as well. I don't want to have to setup a whole Xcode project for simple little apps like this (of which I need to make many that link to my library). Qmake etc. is far more convenient.
hi
i find it quite hard to get gsoap running.
Need to mention my knowledge of C/C++ is quite limited.
In /usr/share/doc/gsoap/ i see
Makefile.c_rules
Makefile.cpp_rules
Makefile.defines
In /usr/share/doc/gsoap/examples :
the README says just make but there is only Makefile.am
So i did make -f Makefile.am
examples/ck$ make -f Makefile.am
/usr/bin/soapcpp2 -I/soapcpp2/import ck.h
and then all the source code is created.
And then??
What is the application?
For my project i just need a WS client, but i guess i better create a server too so i can test it with it.
Hope my question is clear enough.. :-/
greets, florian
The Header File ck.h contains the functions from your service. The gSoap compiler soapcpp2 creates the stubs and skeletons. To create a test-server you can view the documentation on how to create a standalone server. If you compile your standalone-server you will get undefined references because you have to implement the functions from your ck.h file. Take a look at the example from the gSoap documentation. The calc.h file represents your ck.h file. There is also a quick start guide for developing a client and server.
Firstly, I come from Windows-VisualStudio-C++ background. Now I am developing in a Ubuntu environment.
With the help of a Makefile, I built a mymodule.so and copied it to the modules folder within apache. Now, it appears that the module is working fine. But I would like to debug into this module to understand it better.
So, first, is there any way I can get something similar to the Visual Studio debugger type of feel while debugging this module?
Now, i read that i can use gdb to debug into apache modules, can somebody tell me in detail how this is done or point me to some resource that does it.
Ideally, i would like to single step and stuff. I am trying Code::Blocks IDE which has some debugging support. Using the IDE and custom make file, I build the module. Copied it to module location, but how do i debug.
How do i hook to the apache process. Should I use Attach to Process. I tried that with the pid of httpd, but with no success.
Also, while building is there some flag that i should set so that the .so file is debuggable?
I am pretty basic with Linux because i come from windows programming background. Kindly suggest how I go about this.
Thanks in advance,
Arjun
I think you can attach to an apache process using gdb (at 1111, where 1111 is the PID of the process, or in Code::Blocks) and set breakpoints in your module functions, if the module was compiled with debug. You will need to be root or the same user as the apache process.
gcc -g flag is used to build binaries with the debug info.