tensorflow-intel binary packaging
Hi @Craigacp ,

If my understanding is correct you want to build tensorflow-java using pre-built binaries of respective OS and for Linux and Mac it is success but for windows OS there is problem due to .pyd file format. Is that right ?

`tensorflow-intel` is maintained by `intel` team and officially meant for Windows OS. Pinging them for a response.

CC: @TensorFlow-MKL  Yes, that's correct. Our build works just fine for Linux & Mac on multiple platforms, but due to the pyd files it doesn't work on Windows. Hi @Craigacp and @SuryanarayanaY, I am looking into it.  @mraunak , Any update on this?? Hi @Craigacp,

We don't have build for SIG-JVM/TensorFlow-Java. The file type pyd is dynamic link library of Python. What's your expectation for this case? I would suggest to build TensorFlow from source for your specific requirements. Thanks.  We do currently build TF from source. I'd like the libtensorflow and tensorflow framework libraries to be packaged as DLLs, because they are dependently loaded by the actual python binding and so I assume they don't need to be pyd files (because on other platforms they are independent of the API in use). If you package the python `tensorflow-intel` package like that then we can use the binaries you build which will make it easier for us to keep TF-Java up to date. We don't have dedicated build resources, TF-Java uses GitHub actions and the Windows build is something which times out and we also don't have much experience with. 
Hi @craigacp, this is regarding https://discuss.tensorflow.org/t/tensorflow-version-update/22277. My reply on the discuss forum is awaiting some approval. Hence, pasted my comments here

To resolve long path issues while building with Bazel, set --output_user_root=c:\
e.g. bazel --output_user_root=c:\ build --config=opt --repo_env=TF_PYTHON_VERSION=3.10 --define=no_tensorflow_py_deps=true //tensorflow/tools/pip_package:build_pip_package

Apart from this, also consider looking into the system settings to ensure the long path is enabled. https://www.backupery.com/how-to-enable-ntfs-long-paths-in-windows/

For https://github.com/tensorflow/tensorflow/issues/62579, PR from our end is in progress

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.13, 2.14

### Custom code

No

### OS platform and distribution

Windows x86_64

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`tensorflow-intel` is packaged with the TF native libraries stored as pyd files which wrap in some of the Python code. Other versions of tf (e.g. macOS and Linux) package native libraries in the default formats (e.g. `so` or `dylib`). In SIG-JVM/TensorFlow-Java we're planning on redoing our native builds so that we pull in pre-built binaries from the TF python release as that will make our builds much simpler and less error prone, but we can't re-use the Windows builds as the native binary depends on Python symbols. I reached out to SIG-BUILD and they told me to open an issue here. @mraunak

### Standalone code to reproduce the issue

```shell
Download the whl and unzip it.
```


### Relevant log output

_No response_