You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proprietary mesh triangulation in open source software
Proprietary mesh triangulation in open source software?
Recently I was looking for a solid, reliable way to do path triangulation. Looking at state-of-the-art research, I came across the UC Berkley researcher Jonathan Shewchuk's outstanding Triangle library.
Jonathan is very clear on the Triangle website, and in source code, about the project not being open-source:
This program may be freely redistributed under the condition that the copyright notices
(including this entire header and the copyright notice printed when the `-h' switch is
selected) are not removed, and no compensation is received.
Private, research, and institutional use is free.
Because cross-compiling binaries for Windows is easier than building natively
Because cross-compiling binaries for Windows is easier than building natively
I want Microsoft to do better, want Windows to be a decent development platform-and yet, I constantly see Microsoft playing the open source game: advertising how open-source and developer friendly they are - only to crush developers under the heel of the corporate behemoth's boot.
The people who work at Microsoft are amazing, kind, talented individuals. This is aimed at the company's leadership, who I feel has on many occassions crushed myself and other developers under. It's a plea for help.
The source of truth for the 'open source' C#, C++, Rust, and other Windows SDKs is proprietary
You probably haven't heard of it before, but if you've ever used win32 API bindings in C#, C++, Rust, or other languages, odds are they were generated from a repository called microsoft/win32metadata.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
error(compilation): clang failed with stderr: zig: warning: argument unused during compilation: '-nostdinc++' [-Wunused-command-line-argument]
zig: warning: argument unused during compilation: '-nostdinc++' [-Wunused-command-line-argument]
In file included from C:\Users\slimsag\Desktop\zig\zig-out\lib\zig\libcxxabi\src/cxa_aux_runtime.cpp:14:
In file included from C:\Users\slimsag\Desktop\zig\zig-out\lib\zig\libcxx\include\typeinfo:75:
C:\Users\slimsag\Desktop\zig\zig-out\lib\zig\libc\include\any-windows-any\vcruntime_typeinfo.h:121:13: error: target of using declaration conflicts with declaration already in scope
C:\Users\slimsag\Desktop\zig\zig-out\lib\zig\libc\include\any-windows-any\vcruntime_typeinfo.h:69:7: note: target of using declaration
More importantly, WIDL contains patches to generated header files that make e.g. COM calling conventions compatible with mingw-w64 and clang when targetting GNU ABI.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters