Skip to first unread message
Dror Lugasi
Oct 26, 2016, 1:28:19 PM10/26/16
to BeagleBoard
Hello guys..
I have a code i wrote in monodevelop and i have the program .exe file that i want to run after the desktop is loaded.
When i go into the terminal and change the dir to the debug folder and run ./thefile.exe it works.
I have a code i wrote in monodevelop and i have the program .exe file that i want to run after the desktop is loaded.
When i go into the terminal and change the dir to the debug folder and run ./thefile.exe it works.
I tried to add this command to a shell script that i run at boot as
./<full path>thefile.exe
And also cd <full path> and then ./thefile.exe but none has worked.
Can anyone please help me to figure out how to run my .exe file automatically after boot (prefer as root if possible)
Cheers!
Dror.
evilwulfie
Oct 26, 2016, 1:35:22 PM10/26/16
to beagl...@googlegroups.com
.exe files are for windows
Robert Nelson
Oct 26, 2016, 1:35:36 PM10/26/16
to Beagle Board, Dror Lugasi
For example with openbox, there's an autostart script available at:
/home/debian/.config/openbox/autostart
mkdir -p /home/debian/.config/openbox/
echo "feh --bg-scale /opt/scripts/images/beaglebg.jpg" >
/home/debian/.config/openbox/autostart
echo "/home/debian/LeptonModule/software/beagleboneblack_video/bbb &"
>> /home/debian/.config/openbox/autostart
Regards,
--
Robert Nelson
https://rcn-ee.com/
Dieter Wirz
Oct 26, 2016, 2:57:42 PM10/26/16
to beagl...@googlegroups.com
./someexecutable
This means run "someexecutable" in the in the current directory
because ./ is the current directory.
In startup scripts give the full path! without leading point!
e.g.
/home/you/somepath/someexecutable
AND as evilwulfie pinted out, never ever call a unix executable *.exe.
This is evil;)
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f73293bd-454b-4f41-8141-776bf8ca454c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
This means run "someexecutable" in the in the current directory
because ./ is the current directory.
In startup scripts give the full path! without leading point!
e.g.
/home/you/somepath/someexecutable
AND as evilwulfie pinted out, never ever call a unix executable *.exe.
This is evil;)
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f73293bd-454b-4f41-8141-776bf8ca454c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
mickeyf
Oct 28, 2016, 1:10:14 PM10/28/16
to BeagleBoard
Depending on how things are set up, you may need to run not "my_xxx.exe", but "mono my_xxx.exe".
woody stanford
Jan 30, 2017, 3:55:15 PM1/30/17
to BeagleBoard
idk about the whole *.exe thing.
I've found programming ANSI C that its nice to be able to port my MinGW code directly to GCC without changing my build shell scripts (*blushes* well my make files I mean). Hense a lot of my bins on my UN*X have the exe extension.
Seems to work...alignment aside.
Reply all
Reply to author
Forward
0 new messages