Viewing Embeded Command Line Calls

Question

0.00/5 (No votes)

See more:

Hello,

I have been using a windows based IDE with an arm toolchain but have recently migrated to linux. I have several large projects that I can not make a proper makefile for as they throw errors left right and center.

I wish to continue using the same arm compiler because arm and gnu asmbler syntax are different and some of my file are in asm.

Is their a way I can run an app that will monitor everything a program does so I can load my project in the IDE, hit rebuild and know the entire call sequence to the asm, gcc and linker?

I can do this via windows or linux with wine which ever is easier. I tried doing systrace but oh wow thats way to much output and 'ps' with a full thread view does not give enough information.

Thanks!

Posted 1-Jan-11 6:31am

Trevor Johansen

Add a Solution

Comments

Espen Harlinn 1-Jan-11 13:00pm

By large - how many files?
How are they organized?
There are many tools out there that can automagically create makefiles for complex projects ...

Manfred Rudolf Bihy 1-Jan-11 17:36pm

I have made an update to my answer concerning WMIC tool in Windows XP.

3 solutions

Solution 1

My project tree has several folders and outputs obj, lst, lib to seperate directories from around ~40 files.

What programs would you recommended to create a makefile skeleton for a large project? I can make basic makefiles but then theirs a lot of dependencies and output folders the %:.: and .c.o: can get confusing.

Also I ran 'strace wine ide.exe 2>dump.txt' and then 'cat dump.txt | grep armgcc' and I only found references to the files locations. In the IDE i compiled one c file and when I grep for that file I see:

stat64("/home/uminded/.wine/dosdevices/c:/Keil/ARM/Examples/Blinky/Blinky.c", {st_mode=S_IFREG|0644, st_size=1755, ...}) = 0
write(19, "compiling Blinky.c...\r\n", 23) = 23
write(19, "Blinky.c - 0 Error(s), 0 Warning"..., 38) = 38

But I can not find the string that was passed to armgcc.exe to compile Blinky.c

The end goal is to get the project IDE as Code::Blocks but use the arm compiler

Posted 1-Jan-11 7:21am

Trevor Johansen

Solution 2

Some tools that might help:

Cmake at http://www.cmake.org/[^]

ACE MPC som info here:http://www.ociweb.com/products/MPC[^] and download as part of ACE+TAO here http://download.dre.vanderbilt.edu/[^]

Gnu autotools - some info here http://www.lrde.epita.fr/~adl/autotools.html[^]

Hope this helps
Espen Harlinn

Posted 1-Jan-11 7:53am

Espen Harlinn

Comments

Trevor Johansen 1-Jan-11 14:23pm

Oh wow the autotools tutorial is long but excellent. Exactly the info I was looking for on how to make a better makefile thats for sure!

However I still need to find out what command line switches to actually pass to my compiler as its documentation is not spectacular and I can only compile 50% of my programs by hand

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manfred Rudolf Bihy · Accepted Answer · 2011-01-01T11:30:00

Hi Trevor,

I don't know for how long your program runs, but "process explorer" from Sysinternals lets you look at how a program was started including the whole command line. I think it is in the property dialog of a process that can be opened via context menu from the list of processes.
In the property dialog go through the tabs that are there and look around. I think it is on the image tab where the whole command line can be seen. So if you know what the name of the executable is that's doing your compilation stuff you should be all set to go and try that out.
Only problem I see is the program finishing to soon for you to have a chance to find the process and have a look at it.

Good luck!

Modification
On windows XP Professional there is a command line tool to do WMI: http://windowsxp.mvps.org/listproc.htm[^].
On the site above they do it like this:

WMIC /OUTPUT:C:\ProcessList.txt PROCESS get Caption,Commandline,Processid

End of modification
Best regards,

Manfred