Skip to content

Conversation

janisozaur
Copy link
Contributor

FAAD2 lists its homepage as https://sourceforge.net/projects/faac/, but
it links to https://github.com/knik0/faad2 as the place to send pull
requests. This seems good enough for Debian[0] and Arch[1], and the SF
hosts only a bit older versions, so I used the GitHub project as well.

Note that though the project is named "faad2", the library name is just
"faad"

[0] https://packages.debian.org/sid/faad
[1] https://www.archlinux.org/packages/extra/x86_64/faad2/

@janisozaur janisozaur force-pushed the faad2 branch 2 times, most recently from 420e966 to 16ab16b Compare November 14, 2019 10:20
@janisozaur
Copy link
Contributor Author

ping @knik0 @fabiangreffrath

All the attached patches were merged as:
knik0/faad2#42
knik0/faad2#43
knik0/faad2#44

I added a comment to each of the patches with link to pull request.

@NancyLi1013
Copy link
Contributor

/azp run

@NancyLi1013
Copy link
Contributor

Hi @janisozaur thanks for this PR.
This port build failed on Linux and OSX now. Is this expected?
If this port doesn't support these two platforms, please add the related message
vcpkg_fail_port_install(MESSAGE "${PORT} currently only supports Windows platform." ON_TARGET "Linux" "OSX")

If not, please try to fix it.

Thnaks.

@janisozaur
Copy link
Contributor Author

janisozaur commented Nov 21, 2019

I've updated the port. with your suggestions.

I don't intend to target Linux and OSX with this port, but would like to know if there is a way to extract logs of AZP containing failure messages?

@NancyLi1013
Copy link
Contributor

@janisozaur thanks for your updates.
Please refer to the following steps to get the failure logs(For example Linux)
Capture1

Capture2

After you click post build on failure logs, you will download it.

If this port failed due to POST_BUILD_CHECKS_FAILED or other failures that show on the console, you can find the related messages here:
Capture3

Capture4

Hope this help you some.

@fabiangreffrath
Copy link

Needless to say that FAAD2 builds perfectly fine on Debian and any other Linux distribution.

FAAD2 lists its homepage as https://sourceforge.net/projects/faac/, but
it links to https://github.com/knik0/faad2 as the place to send pull
requests. This seems good enough for Debian[0] and Arch[1], and the SF
hosts only a bit older versions, so I used the GitHub project as well.

Note that though the project is named "faad2", the library name is just
"faad"

The embedded patches were all submitted and already merged upstream.

[0] https://packages.debian.org/sid/faad
[1] https://www.archlinux.org/packages/extra/x86_64/faad2/
@janisozaur
Copy link
Contributor Author

As I mentioned earlier, supporting Linux and OS X with this vcpkg is not my goal and I chose to explicitly disable it, as requested. I'm mostly interested in having a sane package manager for Windows and all Windows triplets should now be supported.

@ras0219-msft
Copy link
Collaborator

This LGTM, thanks for the PR @janisozaur!

@fabiangreffrath We don't require initial submitters to support every platform possible; if you'd like to make a PR to enable Linux and OSX that would be awesome!

@ras0219-msft ras0219-msft merged commit 470a70a into microsoft:master Nov 22, 2019
@fabiangreffrath
Copy link

Sorry, but I am just the Debian maintainer for faad2 and don't have any plans to also get involved here.

@oddlf oddlf mentioned this pull request May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants