profile
viewpoint
Daniele D'Orazio d-dorazio @develersrl Firenze, Italy https://d-dorazio.github.io Software developer @develersrl. Interested in programming language design and type theory. Rust & Haskell.

d-dorazio/mattors 5

My generative art playground

d-dorazio/QLogger 4

Qt logger library

d-dorazio/gork 3

ZMachine v3 implementation in Go

d-dorazio/delaunay-mesh 2

An implementation of the Bowyer–Watson algorithm to iteratively construct a Delaunay triangulation

d-dorazio/jv 1

json viewer

d-dorazio/marching-squares 1

marching squares implementation in rust

d-dorazio/r3d 1

playground to learn 3d using Rust

d-dorazio/rd 1

Reaction-Diffusion using the Gray-Scott model

8-Team/micropython-esp32 0

MicroPython ported to the ESP32

create barnchd-dorazio/gerrymandering

branch : master

created branch time in 16 days

created repositoryd-dorazio/gerrymandering

created time in 16 days

startedbevyengine/bevy

started time in a month

create barnchd-dorazio/wasm-webinar-2020

branch : website

created branch time in a month

issue closedlhmouse/mcfgthread

Add way to distinguish 32bit vs 64bit mcfgthread-12.dll

Hi, we're in the process of migrating some binaries to using mcfgthread, but unfortunately we're hitting a roadblock that we're not able to work around easily.

The binaries we're migrating are both 32bit and 64bit and need to live and coexist all in the same directory.

Here's an example tree structure of the binaries

.
├── bin1-32bit.exe
├── bin2-64bit.exe
└── bin3-32bit.exe
└── lib1-32bit.exe
└── lib1-64bit.exe

Ideally we'd like to ship the dll required by mcfgthread in that directory just like we're doing for all the other libraries, but unfortunately we cannot because the name of dll is the same that is mcfgthread-12.dll. This makes effectively impossible to have two binaries for different architectures live in the same directory.

Do you think it might be feasible to change the name of the dll to include the architecture or any other way to distinguish between 32bit vs 64bit?

I realize this would be a breaking change, but if that's a concern (definitely a valid one) we could maybe setup additional pipelines that create the artifacts with the new names while keeping the old ones around for the foreseeable future.

What do you think?

closed time in a month

d-dorazio

issue commentlhmouse/mcfgthread

Add way to distinguish 32bit vs 64bit mcfgthread-12.dll

We will workaround the issue ourselves by changing the directory structure. Thanks for your time.

d-dorazio

comment created time in a month

PublicEvent

push eventd-dorazio/wasm-webinar-2020

push time in 2 months

delete branch d-dorazio/wasm-webinar-2020

delete branch : website

delete time in 2 months

push eventd-dorazio/wasm-webinar-2020

Daniele D'Orazio

commit sha 0aee80ddd5a3a67123f5728a61d1e9c7640964e0

disable wasm-opt

view details

Daniele D'Orazio

commit sha 2b8fe81e2caee01d5914cfe4836af2e669efa4a9

deploy

view details

push time in 2 months

create barnchd-dorazio/wasm-webinar-2020

branch : website

created branch time in 2 months

push eventd-dorazio/d-dorazio.github.io

Daniele D'Orazio

commit sha 0ba9ee082db6c899cffee0b755e3d6b8e442c06e

deploy with newer hugo

view details

push time in 2 months

push eventd-dorazio/d-dorazio.github.io

Daniele D'Orazio

commit sha d2c1d1bcdd307b03334659e149281c748707ac34

deploy with newer hugo

view details

push time in 2 months

issue openedlhmouse/mcfgthread

Add way to distinguish 32bit vs 64bit mcfgthread-12.dll

Hi, we're in the process of migrating some binaries to using mcfgthread, but unfortunately we're hitting a roadblock that we're not able to work around easily.

The binaries we're migrating are both 32bit and 64bit and need to live and coexist all in the same directory.

Here's an example tree structure of the binaries

.
├── bin1-32bit.exe
├── bin2-64bit.exe
└── bin3-32bit.exe
└── lib1-32bit.exe
└── lib1-64bit.exe

Ideally we'd like to ship the dll required by mcfgthread in that directory just like we're doing for all the other libraries, but unfortunately we cannot because the name of dll is the same that is mcfgthread-12.dll. This makes effectively impossible to have two binaries for different architectures live in the same directory.

Do you think it might be feasible to change the name of the dll to include the architecture or any other way to distinguish between 32bit vs 64bit?

I realize this would be a breaking change, but if that's a concern (definitely a valid one) we could maybe setup additional pipelines that create the artifacts with the new names while keeping the old ones around for the foreseeable future.

What do you think?

created time in 2 months

delete branch d-dorazio/circle-packing

delete branch : polyline

delete time in 2 months

push eventd-dorazio/circle-packing

Daniele D'Orazio

commit sha 58fcdad4c2c295a472531d289c777dbe2c72f6e9

shapes: add rough support for polylines Clipping is missing and it doesn't support the even-odd fill rule or anything "standard".

view details

Daniele D'Orazio

commit sha 53d7a374423c4dbb9e92495b818401448bb6f5cc

examples: add logo example to test Polyline

view details

Daniele D'Orazio

commit sha a1936973ad195d4fc06570d3200ba7576eab343b

factor common packing code in lib

view details

Daniele D'Orazio

commit sha 5294a78238981861aea150082c72d295b9bb2ae5

examples: add rombus example

view details

Daniele D'Orazio

commit sha 53359bde04ebc2970624f126a8d386c379d21907

README.md

view details

push time in 2 months

push eventd-dorazio/circle-packing

Daniele D'Orazio

commit sha 982ea4d2400731a027b29db38c04824bf96c950f

factor common packing code in lib

view details

Daniele D'Orazio

commit sha e36f7fca5447d920498b2ab3500de2da1a6e5791

examples: add rombus example

view details

push time in 2 months

push eventd-dorazio/circle-packing

Daniele D'Orazio

commit sha 82565d1ce491708a4a618820b60e2a63ceb22a5e

shapes/polyline: add rough support for holes Clipping is missing.

view details

Daniele D'Orazio

commit sha 2e8c8b5167dcbcbe18d245abd645e92b4d60bedc

examples: add logo example to test Polyline

view details

push time in 2 months

create barnchd-dorazio/circle-packing

branch : polyline

created branch time in 2 months

push eventd-dorazio/circle-packing

Daniele D'Orazio

commit sha aeaa0c9eeb2fe7e3fb4348348d2653e7d2667800

add themes

view details

Daniele D'Orazio

commit sha ff1d605e20b4802760b895343be167faa2e2d84f

add simple cli

view details

push time in 2 months

push eventd-dorazio/circle-packing

Daniele D'Orazio

commit sha b4d6a983ea858ac889142e2da99cb92fac1e1a0b

add parameter to customize whether to allow containing circles or not

view details

push time in 2 months

create barnchd-dorazio/circle-packing

branch : master

created branch time in 2 months

created repositoryd-dorazio/circle-packing

dead simple circle packing algorithm

created time in 2 months

delete branch d-dorazio/quark

delete branch : patch-1

delete time in 2 months

PR opened comelz/quark

fix typos
+2 -2

0 comment

1 changed file

pr created time in 2 months

push eventd-dorazio/quark

Daniele D'Orazio

commit sha 518a07632d566700c8efa4371522cf779a18be13

fix typos

view details

push time in 2 months

fork d-dorazio/quark

Simple project dependency management

fork in 2 months

push eventd-dorazio/chip8

Daniele D'Orazio

commit sha 7815771e8d348b6da07327d5c686b21e18917891

chip8: deploy

view details

push time in 3 months

push eventd-dorazio/chip8

Daniele D'Orazio

commit sha 54e5f916d3e8f5324aa1cce4278b105b850eae00

cargo update

view details

Daniele D'Orazio

commit sha 1922bfcb1fbad0eef4294eb7b56ccc0d0e95dfb1

chip8: npm update

view details

Daniele D'Orazio

commit sha 4858eda0fdca3e6108b8853f56bc77f6120ffbb2

chip8: deploy

view details

push time in 3 months

push eventd-dorazio/dotfiles

Daniele D'Orazio

commit sha 4ac9469760a3a9b2fa377c8edfda373748ed4106

install: node 12

view details

push time in 3 months

more