I personaly create a CAB file with the 3 cegcc DLLs incorporated to distribute my application and ease its installation. If there were several versions of those DLLs, packaging would be harder. So could it be possible for those DLLs to detect on which WinCE version they run and dynamically provide the sets of API that are available of each WinCE ? Maybe this is unrealistic, I don't know.
Pascal Danny Backx a écrit : > Pedro, others, > > Would it be a good idea to generate multiple versions of some of the > libraries that we distribute ? > > An example : the line > ./mkimport.sh $defdir/coredll.def $outputdir || exit > in src/cegcc/importlibs/build.sh creates > /opt/cegcc/arm-wince-cegcc/lib/libcoredll.a > based on the input file src/cegcc/importlibs/defs/coredll.def whose > contents is a list of supported APIs. > > As we know several versions of WinCE are popular, we only distribute one > version of our toolset. > > We could have support for more than one version of WinCE by creating a > second version of coredll.def and having an additional line in build.sh, > such as > ./mkimport.sh $defdir/coredll5.def $outputdir || exit > > We could even have a "master" file that defines multiple OS levels, and > generate coredll.def, coredll5.def and so on from it. > > How good or bad an idea is this ? > > Danny > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
