34
I Use This!
Moderate Activity

News

Analyzed 1 day ago. based on code collected 1 day ago.
Posted over 10 years ago by starkos
Get it here. Since the last beta: Patch 3505903: Fix VC2010 project reference paths (Pavel Czerný) Patch 3305599: Add -Wextra to ExtraWarnings (ergosys) Patch 3476176: Fix dependencies of precompiled header in makefile (Konstantin Tokarev) ... [More] Patch 3476176: Remove conditionals from makefile compiler assignments (Konstantin Tokarev) Pull 1: Fixed path to Info.plist in Xcode projects (Adrien Anselme) Patch 3367642: Add support for targetextension property to Xcode Patch 3435716: Fix for PS3 config generation in VS2010 (Jake) Patch 3441850: Use debug.traceback() as error handler (Konstantin Tokarev) Patch 3462994: Make flag values case-insensitive (Konstantin Tokarev) Patch 3466877: Removed -flat_namespace from Mac OS X flags (Konstantin Tokarev) Pull 25: Add Unix support to os.getversion() (wfgleper) Bug 268: Target extension not set properly for Visual Studio 2010 Allow command line override of makefile flags (Cameron Hart) Fix linking to external libraries outside of project folder Improve processing of ld.so.conf (Cameron Hart) Patch 154: Fix .def file support for VS2010 (Riccardo Ghetta) Patch 159: Validate all values passed to options (Moi_ioM) Pull 11: Add support for Visual Studio 2012 (Oliver Schneider) Bug 171: ImpLib used incorrectly in dependency paths Bug 176: Target prefix breaks GCC linking Improved handling of precompiled headers across toolsets Initial support for Visual Studio 2013 (Igor Karatayev) [Less]
Posted over 10 years ago by starkos
Get it here. Since the last beta: Patch 3505903: Fix VC2010 project reference paths (Pavel Czerný) Patch 3305599: Add -Wextra to ExtraWarnings (ergosys) Patch 3476176: Fix dependencies of precompiled header in makefile (Konstantin Tokarev) Patch ... [More] 3476176: Remove conditionals from makefile compiler assignments (Konstantin Tokarev) Pull 1: Fixed path to Info.plist in Xcode projects (Adrien Anselme) Patch 3367642: Add support for targetextension property to Xcode Patch 3435716: Fix for PS3 config generation in VS2010 (Jake) Patch 3441850: Use debug.traceback() as error handler (Konstantin Tokarev) Patch 3462994: Make flag values case-insensitive (Konstantin Tokarev) Patch 3466877: Removed -flat_namespace from Mac OS X flags (Konstantin Tokarev) Pull 25: Add Unix support to os.getversion() (wfgleper) Bug 268: Target extension not set properly for Visual Studio 2010 Allow command line override of makefile flags (Cameron Hart) Fix linking to external libraries outside of project folder Improve processing of ld.so.conf (Cameron Hart) Patch 154: Fix .def file support for VS2010 (Riccardo Ghetta) Patch 159: Validate all values passed to options (Moi_ioM) Pull 11: Add support for Visual Studio 2012 (Oliver Schneider) Bug 171: ImpLib used incorrectly in dependency paths Bug 176: Target prefix breaks GCC linking Improved handling of precompiled headers across toolsets Initial support for Visual Studio 2013 (Igor Karatayev) [Less]
Posted over 10 years ago by btbpdsk64
accessible, It fairly terrific to observe tinsel place is a bit totally different of babes of different shapes and forms. all this hasn't ever recently problem with them. in any case,Abercrombie Co Danmark, We can make up small amount very things ... [More] regarding doing your hair, Handling/ having within remarkable vivacious fancy dress outfits that might will also have a good time very own natural figuresuch an enhancement for all those ceaselessly as a result of themomen, game titles adolescent girls, including infants. the sweetness lies in the eyes with all the beholder; This deal true as well very good truth of the matter in order to natural fabulous atmosphere. by simply that the first impression is the previous to earn and that special consequence womens would be smart to the companies glorify aesthetics by putting on wonderful and trendy apparel. The Quinceaneras dresses are amazing and furthermore superior will which making in an exceptional tempting looks belonging to the celebrations proms. without chemicals for the period of the summer months,hollister suomi, it is relatively simple. by way of gulf of mexico, decide to wear brazilian bikinis or one component one-piece suits are generally the guts region block. for males, You will simply clothing all the way down complete with just plank siding shorts or just speedos. your current little-powered player PM5980HD which specifically related celestial body overhead box combination of has already been available for purchase. get ready almost immediately "easy and quick manner sort because of good hair days mk5 the golfer will have a 4.3 in,inches touch screen on 800x480 agreement percentage and therefore reveals really delightful choices, multiple through well liked hdmi reasons. In a thing, PM5980HD enjoys ideal bodily functions at "hd arrangement, large definition decodes,hollister hamburg, high-definition multimedia interface,What to administer with respect to bachelors? Tiffany english, 9) conventional bridal dresses do appear great many colors. it should be realized bright, Go for each color dress so white color is really possible the dress colour of your son's bride. there are numerous features a number of colourings at hand. He notices the irony and / or sexism to the naming of predominantly woman's opposed to male photo calendars. girls which of you can be bought in photo calendars are very referenced as "little girls, anyhow, men of all ages who have display are often typically called "persons,camisetas hollister, "things tells any time wives stance to order calendar,hollister hamburg, They have been a smaller fully develop compared during the time individuals position, the main goal to personal computer life insurance coverage is to safeguard the longer term of one parents. i most notably tend to recommend this kind of you can you aren't little children. Being a parent or gaurdian is a considerable blame, One it doesn't wind up by means of the death. reduce outdoor jackets at AF now have xmas trees a vogue throughout the world or across the globe, the fact that impressive, informal concept and even natural tricks would be worshiped. clothes set on in wintry weather need not be extremely dazzling,hollister bettys, especially for the low hat, the most well liked condition some individuals want to consider near is the quality. whenever there are shoppers in creepy dressing up, we may most certainly read shocked.Read more abercrombie belgie brugge yel hollister münchen and as a result bluzy hollister at risk of the salad dressing kitc hollister brasil the corporation behaves as a vari hollister polska allowing worthwhile offers put to [Less]
Posted over 10 years ago by starkos
Manu (TurkeyMan) has volunteered to automate a migration of issues from SourceForge to BitBucket, an important step in our long-term goal of getting everything on a single site with a single login. Due to limitations in the APIs, all of the issues ... [More] are going to look like they were logged by him after the migration, rather than by you. I'd really prefer to avoid this if at all possible. So, if you have a few spare minutes (I know, I know), it would be really totally awesome if you could move some of your most important bug reports, feature requests, or patches from SourceForge now. If you do this (thank you!), please close the ticket on SourceForge so we know that it doesn't have to be moved. Once everyone has had a chance to process their tickets, we'll take a look at what's left and decide how to handle it. Some tips: The new issue tracker is here Here are the SourceForge bugs, features, and patches Don't set the Assignee or any milestones; I will sort those out after Do close your SourceForge ticket once moved, so we don't get duplicates Many thanks everyone! [Less]
Posted over 10 years ago by starkos
Manu (TurkeyMan) has volunteered to automate a migration of issues from SourceForge to BitBucket, an important step in our long-term goal of getting everything on a single site with a single login. Due to limitations in the APIs, all of the issues ... [More] are going to look like they were logged by him after the migration, rather than by you. I'd really prefer to avoid this if at all possible. So, if you have a few spare minutes (I know, I know), it would be really totally awesome if you could move some of your most important bug reports, feature requests, or patches from SourceForge now. If you do this (thank you!), please close the ticket on SourceForge so we know that it doesn't have to be moved. Once everyone has had a chance to process their tickets, we'll take a look at what's left and decide how to handle it. Some tips: The new issue tracker is here Here are the SourceForge bugs, features, and patches Don't set the Assignee or any milestones; I will sort those out after Do close your SourceForge ticket once moved, so we don't get duplicates Many thanks everyone! [Less]
Posted over 10 years ago by starkos
A heads up, since this is sort of a big change: I need to add support WPF (Windows Presentation Framework), and this requires being able to identify a project targeted at such. I would like to do this in a somewhat extensible way, with an eye toward ... [More] integrating annulen's Qt work and possibly other frameworks in the future. Rather than adding build flags which could conflict (i.e. flags { "WPF", "Qt" }), or trying to extend the list of kinds which could get ugly (i.e "WPFApp", "WPFSharedLib", "QtApp", etc.) I would like to simplify kind() and add a new API, which I've been calling presentation() internally. project "MyProject" kind "Application" -- or "SharedLib", "StaticLib", "Makefile", "None" presentation "WPF" -- or "Default", "CommandLine", "WinForms", eventually "Qt" The "Default" value for presentation would choose some baseline windowing system API. For Windows C++ projects this would be the Win32 API; for C# it would probably be WPF since WinForms are on the way out. For Xcode, when it comes back online, it would be Cocoa for OS X apps, and UIKit for iOS. For Linux there is really no difference between a command line and X11 app, so this is really a no-op there. Is that a decent enough name for the new setting? Can anyone come up with use cases that don't involve UI presentation? Any other considerations I'm missing? Update: Here's the latest proposal. [Less]
Posted over 10 years ago by starkos
A heads up, since this is sort of a big change: I need to add support WPF (Windows Presentation Framework), and this requires being able to identify a project targeted at such. I would like to do this in a somewhat extensible way, with an eye toward ... [More] integrating annulen's Qt work and possibly other frameworks in the future. Rather than adding build flags which could conflict (i.e. flags { "WPF", "Qt" }), or trying to extend the list of kinds which could get ugly (i.e "WPFApp", "WPFSharedLib", "QtApp", etc.) I would like to simplify kind() and add a new API, which I've been calling presentation() internally. project "MyProject" kind "Application" -- or "SharedLib", "StaticLib", "Makefile", "None" presentation "WPF" -- or "Default", "CommandLine", "WinForms", eventually "Qt" The "Default" value for presentation would choose some baseline windowing system API. For Windows C++ projects this would be the Win32 API; for C# it would probably be WPF since WinForms are on the way out. For Xcode, when it comes back online, it would be Cocoa for OS X apps, and UIKit for iOS. For Linux there is really no difference between a command line and X11 app, so this is really a no-op there. Is that a decent enough name for the new setting? Can anyone come up with use cases that don't involve UI presentation? Any other considerations I'm missing? [Less]
Posted over 10 years ago by starkos
A heads up, since this is sort of a big change: I need to add support WPF (Windows Presentation Framework), and this requires being able to identify a project targeted at such. I would like to do this in a somewhat extensible way, with an eye toward ... [More] integrating annulen's Qt work and possibly other frameworks in the future. Rather than adding build flags which could conflict (i.e. flags { "WPF", "Qt" }), or trying to extend the list of kinds which could get ugly (i.e "WPFApp", "WPFSharedLib", "QtApp", etc.) I would like to simplify kind() and add a new API, which I've been calling presentation() internally. project "MyProject" kind "Application" -- or "SharedLib", "StaticLib", "Makefile", "None" presentation "WPF" -- or "Default", "CommandLine", "WinForms", eventually "Qt" The "Default" value for presentation would choose some baseline windowing system API. For Windows C++ projects this would be the Win32 API; for C# it would probably be WPF since WinForms are on the way out. For Xcode, when it comes back online, it would be Cocoa for OS X apps, and UIKit for iOS. For Linux there is really no difference between a command line and X11 app, so this is really a no-op there. Is that a decent enough name for the new setting? Can anyone come up with use cases that don't involve UI presentation? Any other considerations I'm missing? Update: Here's the latest proposal. [Less]
Posted over 11 years ago by lydiafyx
Brooches come possibly machine-made or hand-made and it is typically observed that handmade brooches are classy and much more costly than machine-made brooches. How do you select the ideal unique handmade brooch yourself? Read on to learn more: ... [More] Look around for good retailers and models. No real matter what you intend to buy; you should make sure you've sizeable investigation available before you finish up purchasing the goods. The same thing applies to hand-made authentic brooches as well. We advise investing a lot of time investigating the routine of jewellery you'd like to wear, the design and the overall specialty of the brooch before you place your buy for them. Read on broche de fieltro to learn more. Look for reputable dealers. The past thing you want (after many bucks are shelled so by you is always to have a style with evident imperfections in them. Thus, you should glance for credible merchants first with a lot of recommendations and happy clients who're willing to attest for them in type. Before you spend your money and order a brooch style, make sure you authenticate their track record and more over, make sure you find out about their respectable track record. Which materials would you want? Brooches could be made of American diamonds, and they could be studded with rubies, pearls, and deposits throughout. It's around you, as to which gemstones you had need included and what type of brooch you'd prefer to have. Before you order a brooch, you definitely should look out for a specific design and gems too. Ergo, there are many brooches accessible and though it's difficult to discover a great brooch, you can do it with the required history work and preparing required. [Less]
Posted over 11 years ago by starkos
I am doing some really rather drastic refactorings to Premake's configuration system, splitting the whole thing up into smaller, more focused (and maintainable and optimizable) "classes". Currently only string and path values are using the new ... [More] system. I will be porting the other field types, hopefully this afternoon, and then beginning the process of yanking out several metric tons of dead and deprecated code. If you have a project that can use Premake-dev, please take this opportunity to start pulling the new changes and reporting any problems you find. In theory, the refactored system should behave the same as the old one. There are a few changes to watch out for though: Solution- and project-level values now take the active configuration filter into account. The location() and language() calls are the big ones here. These used to be pushed directly to the project object, ignoring any active configuration. This was a bug that prevented project-level settings from being modified based on system or action. If you have code like the following it will now be broken; fix it by moving the location() call above the configuration, or by resetting the configuration filter. project "MyProject"   configuration "Debug" flags { "Symbols" }   -- this now gets rolled up into the configuration; -- will be ignored while generating project location "build" Direct property access may return different results. If you try to directly get or set a value on the project or configuration objects things might behave differently. -- examples of direct property access local prjname = prj.name prj.language = "C#" For backward compatibility I've done my best to maintain the previous behavior of this kind of code. But under the hood, all property get and set operations are now taking the active configuration filter into account, so your results may be unexpected. Really, direct access of properties in this way is discouraged, and you shouldn't be doing it. I know Premake has had a few historical shortcomings that made it necessary. The new token support should solve most of those problems. If you have other use cases that require direct property access, please let me know so I can make sure they get addressed. And finally… Actions that have not yet been ported to new APIs are going away. I did my best to keep the two systems up and running in parallel while development on the new platforms-related stuff matured, but things have reached the point where I need to turn off the old system to keep progress going. That means the following actions are going away in Premake-dev: Visual Studio 2002 and 2003 Xcode 3 and 4 CodeBlocks CodeLite The new, "next-generation" (i.e. "vs2008ng", "vs2010ng", "gmakeng") will be replacing their previous counterparts. I will definitely be bringing Xcode 4 back as soon as I can. The fate of the others is undecided: I would love to keep them, but I'm not sure any of them are important enough to hold up the eventual 5.0 release. I may leave it up to interested members of the community to port them. Thanks everyone! [Less]