sam/awl
sam
/
awl
1
0
Fork 1
Code Issues 5 Pull Requests Actions Packages Projects Releases 27 Wiki Activity

Windows (and Plan 9) DNS Config #17

Merged
sam merged 4 commits from windows-DNS into master 2022-06-30 22:37:09 +00:00
Conversation 5 Commits 4 Files Changed 9 +195 -6
sam commented 2022-06-29 23:16:04 +00:00
Owner
Copy Link

Newer version should compile properly, Plan 9 will be tested more when I have free time

Would close #14, #15

Newer version should compile properly, Plan 9 will be tested more when I have free time Would close #14, #15
grumbulon commented 2022-06-30 00:02:06 +00:00
Collaborator
Copy Link

You can "cross-compile" by doing this

GOOS=windows GOARCH=amd64 go build

which builds it for Windows

image

HOWEVER

This may be a failure on my end using wrong compile flags but...

this was "resolved" by building it on the windows vm directly and then it actually ran as expected

image

Since Windows docker containers cannot be ran on Linux, most likely anything Windows related will need to be tested on Windows directly either in a vm or some other solution.

You can "cross-compile" by doing this `GOOS=windows GOARCH=amd64 go build` which builds it for Windows ![image](/attachments/6c7fcbf1-61b3-4561-bb76-745f850c47be) HOWEVER This may be a failure on my end using wrong compile flags but... this was "resolved" by building it on the windows vm directly and then it actually ran as expected ![image](/attachments/6c0648b1-e113-48da-899c-a3c07ba1414f) Since Windows docker containers cannot be ran on Linux, most likely anything Windows related will need to be tested on Windows directly either in a vm or some other solution.
image.png
100 KiB
image.png
42 KiB
grumbulon commented 2022-06-30 02:31:39 +00:00
Collaborator
Copy Link

On further investigation this seems to be because of specific build constraints in the /x/sys/windows package

image

This means it is refusing to build on Linux which I thought we could mitigate by including our own build constraints.

So I pulled the windows stuff into it's own file and attempted to build the project with the following

//go:build windows && amd64
// +build windows,amd64

so it would only build the file on windows/amd64 however I now get

imports git.froth.zone/sam/awl/port: build constraints exclude all Go files in /home/grumb/programming/awl/port

which explains why I could only build it on the windows vm or with GOOS windows the /x/sys/windows/ package refuses to build unless GOOS=windows.

On further investigation this seems to be because of specific [build constraints](https://pkg.go.dev/go/build#hdr-Build_Constraints) in the /x/sys/windows package ![image](/attachments/76da4f6a-68a2-4aa5-b971-05a563dd653c) This means it is _refusing_ to build on Linux which I thought we could mitigate by including our own build constraints. So I pulled the windows stuff into it's own file and attempted to build the project with the following ``` //go:build windows && amd64 // +build windows,amd64 ``` so it would only build the file on windows/amd64 however I now get ``` imports git.froth.zone/sam/awl/port: build constraints exclude all Go files in /home/grumb/programming/awl/port ``` which explains why I could only build it on the windows vm or with GOOS windows the /x/sys/windows/ package refuses to build unless GOOS=windows.
image.png
223 KiB
sam changed title from WIP: Windows DNS Config to WIP: Windows (and Plan 9) DNS Config 2022-06-30 12:00:00 +00:00
sam changed title from WIP: Windows (and Plan 9) DNS Config to Windows (and Plan 9) DNS Config 2022-06-30 12:01:01 +00:00
sam commented 2022-06-30 12:01:40 +00:00
Author
Owner
Copy Link

There's some preproccessor magic I looked into, I think it works now (at least it did to me, but more samples would be appreciated)

There's some preproccessor magic I looked into, I think it works now (at least it did to me, but more samples would be appreciated)
🎉 1
grumbulon commented 2022-06-30 12:29:22 +00:00
Collaborator
Copy Link

I built awl and it worked both on the windows vm and when ran with wine, no other issues on my end building or running.

I built awl and it worked both on the windows vm and when ran with wine, no other issues on my end building or running.
sam force-pushed windows-DNS from b6359ed047 to 2e2d5187d1 2022-06-30 22:32:38 +00:00 Compare
sam commented 2022-06-30 22:36:01 +00:00
Author
Owner
Copy Link

Tests all look good, merging

Tests all look good, merging
sam merged commit 220964fc02 into master 2022-06-30 22:37:09 +00:00
sam deleted branch windows-DNS 2022-06-30 22:37:10 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

I am too lazy to do this myself but I will gladly look at someone else's effort

  
invalid

Something is wrong

  
Priority: High

This should be worked on soon

  
Priority: Low

This might get worked on

  
Priority: Medium

This should be worked on eventually

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
Priority: High
Priority: Low
Priority: Medium
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sam/awl#17
No description provided.
Delete Branch "windows-DNS"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?