Wine-independent native Linux application(or, install a Winelib app thatīrings its own Wine). What would be cool though, is if Wine's msi could install a completely Have msi started up, a wineprefix decision is done already. Installing into a different wineprefix won't work, I think. Regarding desktop integration with win32 apps is concerned, I think those I sort of like and dislike the idea at the same time Stefan Dösinger writes in with his thoughts: I don't see why we can't add things like X11Desktop tables and the like. Their own extensions, for example, InstallShield have their ownĮxtensions to support self-registration of DLL's via (something like) The main MSI data is essentially just a database. Reece Dunn follows up with more information about MSIs
Since a lot of that functionality would be abstracted into Wine itself. Moreover, there'd be less ofĪ need to create custom Wine packages for applications like Picassa
msi file could be a true universal installer forīoth Windows machines and Linux machines. Or even instructions to install into a completely independent Wine prefix. Instructions like what windows version to use, a custom. Metadata in an MSI file? Windows would ignore it, but applicationĭevelopers could use it to include some helpful Linux-specific Wine What if we created a standard for passing some sort of wine-specific The thread didn't seem to end in any action items but its an interesting thought nonetheless. Scott Ritchie writes in with an interesting idea about MSI installers. Shows that the CPU time is spent in the Cuda driver(on behalf of both theįAH and X11 processes).
System monitor it shows FahCore_11.exe using ~50% (one full core) and I assume this says that libcuda is using 88% of the CPU andįahCore_11.exe is using 7%. I ran oprofile (first time, never heard of it before) while the client Or less of a single core to feed the GPU leaving the second core free. In Windows this client only uses about 20% (dual core system) are running at 100% and the system is not usable The main problem as stated before is that both cores I have been able to run the GPU client for aboutĪ week now with comparable performance to the same hardware running With Stefan Dosinger's help it may be that we found a bug in the linux cuda implementation. Sadly it seemed that the wrapper somehow caused CPU usage to spike to 100%. There was then some discussion about doing actual testing. I don't have a CUDA enabled card so I can't test anything. If anyone would like to test out different CUDA apps with this and report any feedback it would be much appreciate. Still need to implement a few functions and the direct3d calls but nearly everything is there. Ok, I'm pretty sure I've got a working wrapper. Seth Shellnut has been hard at work making that CUDA wrapper work and has written in with some success! * Restructurations of state handling in Direct3D.Ī friendly reminder for all those who are interested that WineConf 2008 is approaching quickly! Head over to the official * Control panel improvements and new appwiz panel. The Wine development release 1.1.2 is now available.
Courtesy of some excellent summer of code students we're seeing big changes in gdi and the control panel as well as big movements in msxml and direct 3d.
The second development branch release since Wine 1.0 was released recently. 5 posts in 4K by dmitry at (Dmitry Timoshkov).5 posts in 6K by juan.lang at (Juan Lang).