Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Making a python package and cross-platform compatible Post 302863445 by RedEyedDog on Monday 14th of October 2013 08:52:47 AM
Old 10-14-2013
Making a python package and cross-platform compatible

Hi Ive been trying for days now and i just cannot work this out.

Can someone please tell me if im doing this right.

I've written some python3.3 code and now i want to transfer it to an embedded computer to execute.

My OS is a : Debian GNU/Linux 6.0.7 (squeezez) 32-bit kernel

Quote:
Compiler gcc 4.4.4 and gcc 4.4.5

The target computer is : Linux 2.6.9 32bit cpu.
Compiler gcc 3.3.2

So i have the .py files. I install cx_freeze with python3.3.

I then use cxfreese file.py, which create a folder called dist with a bunch of files and a executable.

Now from my understanding everything it needs to run is inside that folder?
So how come when i transfer over to the target computer it says " cannot execute binary file"

is this todo with them haveing diffrent compilers? how do i update the target computers compiler when there is no apt-get or dpkg facility?

Please someone save
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cross platform Authentication

I am looking to have UNIX authenticate against Active Directory in a Windows Server 2003 environment, any suggestion? I am very new to UNIX, 2 weeks worth knowledge, if that. Thanks! (3 Replies)
Discussion started by: Optik
3 Replies

2. Shell Programming and Scripting

configuring packages for cross-platform build

Hi all, I wish to build a few packages for my embedded target running linux over ARM9. It would be tough for me to compile my packages on target so I need to build on a host machine and then transfer the generated binaries. So I got the source-tarball for the packages I need. Now here are my two... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

3. Shell Programming and Scripting

making code compatible to previous bash versions

First let me explain the scenario I have tywo files as usual file1.txt (it has n rows and 8 columns) $1 $2 $3 $4 $5 $6 $7 $8 Code: 1234567|iufgt|iuoy|iout|white |black |red |90879 1234567|iufgt|iuoy|iout|green |pink |blue |90879... (3 Replies)
Discussion started by: s.deepak
3 Replies

4. UNIX for Dummies Questions & Answers

Really simple cross-platform database?

I'm looking for a really simple to use lightweight database. Ideally something open-source that stores data in a (semi-) human-readable format, in case the software isn't working. Something cross-platform enough that I can use it on my Linux machine, my Mac, or stick it on a USB stick and... (2 Replies)
Discussion started by: emdan
2 Replies

5. Debian

Making a python package and cross-platform compatible

Hi Ive been trying for days now and i just cannot work this out. Can someone please tell me if im doing this right. I've written some python3.3 code and now i want to transfer it to an embedded computer to execute. My OS is a : Debian GNU/Linux 6.0.7 (squeezez) 32-bit kernel ... (0 Replies)
Discussion started by: RedEyedDog
0 Replies
WINEGCC(1)						      Wine Developers Manual							WINEGCC(1)

NAME
winegcc - Wine C and C++ MinGW Compatible Compiler SYNOPSIS
winegcc [options] infile... DESCRIPTION
winegcc is a gcc wrapper which tries to provide a MinGW compatible compiler under Linux. This is most useful to Win32 developers who can simply take their MinGW code from Windows, and recompile it without modifications under Winelib on Linux. wineg++ accepts mostly the same options as winegcc. The goal of winegcc is to be able to simply replace gcc/g++/windres with winegcc/wineg++/wrc in a MinGW Makefile, and just recompile the application using Winelib under Wine. While typically there are small adjustments that must be made to the application source code and/or Makefile, it is quite easy to do them in a fashion that is compatible between the MinGW and Wine environments. This manual will document only the differences from gcc; please consult the gcc manual for more information on those options. OPTIONS
gcc options: All gcc options are supported, and are passed along to the backend compiler. -Bprefix This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. This is a standard gcc option that has been extended to recognize a prefix ending with '/tools/winebuild', in which case winegcc enters a spe- cial mode for building Wine itself. Developers should avoid prefixes ending with the magic suffix, or if that is not possible, sim- ply express it differently, such as '/tools/winebuild/', to avoid the special behaviour. -fno-short-wchar Override the underlying type for wchar_t to be the default for the target, instead of using short unsigned int, which is the default for Win32. -mconsole This option passes '--subsystem console' to winebuild, to build console applications. It is the default. -mno-cygwin Use Wine's implementation of MSVCRT, instead of linking against the host system's libc. This is necessary for the vast majority of Win32 applications, as they typically depend on various features of MSVCRT. This switch is also used by the MinGW compiler to link against MSVCRT on Windows, instead of linking against Cygwin's libc. Sharing the syntax with MinGW makes it very easy to write Make- files that work under Wine, MinGW+MSYS, or MinGW+Cygwin. -municode Set the default entry point of the application to be the Unicode wmain() instead of the standard main(). -mwindows This option adds -lgdi32, -lcomdlg32, and -lshell32 to the list of default libraries, and passes '--subsystem windows' to winebuild to build graphical applications. -nodefaultlibs Do not use the standard system libraries when linking. These include at a minimum -lkernel32, -luser32, -ladvapi32, and any default libraries used by the backend compiler. The -mwindows option augments the list of default libraries as described above. -nostartfiles Do not add the winecrt0 library when linking. -Wb,option Pass option as an option to winebuild. If option contains commas, it is split into multiple options at the commas. DEFINES
winegcc defines __WINE__, for code that needs to know when it is being compiled under Wine. It also defines WIN32, _WIN32, __WIN32, __WIN32__, __WINNT, and __WINNT__ for compatibility with MinGW. BUGS
The dllimport/dllexport attributes are not supported at the moment, due to lack of support for these features in the ELF version of gcc. Static linking is not currently supported against Wine's DLL. As a result, the -static, --static, and -Wl,-static options will generate an error. AUTHORS
winegcc was written by Dimitrie O. Paun. SEE ALSO
gcc(1), winebuild(1), wrc(1), wine(1), Winelib User Guide, Wine Developers Guide. Wine 1.2-rc6 October 2005 WINEGCC(1)
All times are GMT -4. The time now is 08:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy